Totally agree with you on that one. What was the resolution??
At least you were inside! Hope YOU took personally responsibility to make YOUR inconvenience better
Are we 100% sure these guests were penalized for this fiasco?
I'm sure not all of them were, but just based on how events like this tend to unfold, I would guess a size-able number of cards were charged...most likely for the earliest reservation times EDIT: the earliest times that coincided with the start of the admittance problem, of course.
Makes sense. I would have assumed there are procedures in place to prevent the charge in the event of this type of event
You would think...but then again we seem to say that about a lot of things related to Disney lately. Simplest solution is for them to have a way to just disable that charge across the board, but who knows if that actually exists.Makes sense. I would have assumed there are procedures in place to prevent the charge in the event of this type of event
DLR uses paper tickets with barcodes on them. Every turnstile has a ticket printer and can print out an official ticket card when a barcode is scanned. Unfortunately WDW does not have this.... they use a completely different system.
If they shared that information they'd be idiots since it would help hackers develop exploits. Did you read the news this week regarding the breach of one of Capital One's S3 buckets? How did the attackers even know that data was there, much less in a misconfigured bucket?
I would have assumed that there are procedures in place to prevent the automated ticket system from going down, or if it did, to get guests thru the tapstiles anyway.Makes sense. I would have assumed there are procedures in place to prevent the charge in the event of this type of event
Disneyland and WDW work tickets entirely differently. At WDW, there are touch-points and finger scans. The only time they'll take a photo of a guest is if they can't or refuse to use the finger scan. Then a CM with an iPad comes over, scans your admission media and takes a photo. After that, the guest has to request a CM with an iPad to enter every time they want to go to a park. DL uses barcode and photo, no finger scan.
No I'm not. The parameters of risk management were codified long after I graduated, so I didn't learn it through formal schooling either but rather on-the-job as the discipline evolved. Regardless, that's irrelevant. It is what it is, and if you are are making comments about it you should know it.
Again: Controls and contingencies need to be in place in proportion to the incidence and severity of the risk.
Do you have any stocks? Do you own any funds? Do the schools your children go to get any grants or partnership from any corporations? Do you work for a publicly owned company?
Not just on Twitter.
But again, you've got a mature perspective. Evidently, not everyone feels that that is necessary.
If I remember correctly, they have their own private cloud. I don't think they've moved any major systems to AWS.
Further, this sort of ties in to what my some of biggest complaints are in regards to the IT department...things that should be common sense are made way more complex than they need to be. As a simple (unrelated) example, many people who visit WDW need to look at dining menus prior to choosing a restaurant. Why are the menus separated into different pages for each meal when it would make the guest experience better to have them on the same page with visual dividers? Why do we have to go back to the restaurant's main page to make a reservation when it would be a better guest experience to be able to do so from the menu page as well? The Disney website loads really slowly, and the "Stitch Ate the Page" error is ridiculously common, so why force guests to change pages more often than necessary?Makes sense. I would have assumed there are procedures in place to prevent the charge in the event of this type of event
