They canceled FP's AGAIN!

[mom2rtk]

How many times have you said that?

A couple. (dozen?...... hundred?)

 

[jpeden]

I'm curious as to what the safe cut off time would be for party nights to NOT make a fp

My wife and I have a 5:25 - 6:25 FP+ for Mine Train and it has not been affected on 9/15. I would say that seems to be the latest allowed time. We do have party tickets (not sure if it makes a difference).

 

[themommy]

My wife and I have a 5:25 - 6:25 FP+ for Mine Train and it has not been affected on 9/15. I would say that seems to be the latest allowed time. We do have party tickets (not sure if it makes a difference).

Close 5:30 to 6:30 is still ok.

 

[usnuzuloose]

Why bother with a FP if all they are going to do is cancel stuff? They want to micro manage you and then you make your times your suppose and then they change it.

 

[MakiraMarlena]

They're cancelling all FPs at MK that end after 6:30. The last window you can keep is 5:30-6:30. But apparently they did not fix it so that they couldn't continue to be booked. So more booking is going on, and more cancellations.

 

[GreatLakes]

I thought it was fairly common knowledge now that Disney cancels FP+ reservations that go past 6:30 on party days. They should update their system so they aren't offered, and I would assume that change is in the queue and will be made shortly, but until then just don't make the reservation to begin with.

I get that it is annoying but not worth getting upset over. It isn't a cancer diagnosis, it is a ride reservation. I wouldn't let it ruin my day.

 

[ohiotodds12]

I got a note that my fast passes for Haunted Mansion were cancelled for 9/22. The only thing is, we didn't have HM on 9/22, we leave that day and are at HS that morning. I looked through all our days and none had been effected so I am not sure what they are talking about this time!

 

[ArwenMarie]

I thought it was fairly common knowledge now that Disney cancels FP+ reservations that go past 6:30 on party days. They should update their system so they aren't offered, and I would assume that change is in the queue and will be made shortly, but until then just don't make the reservation to begin with.

I get that it is annoying but not worth getting upset over. It isn't a cancer diagnosis, it is a ride reservation. I wouldn't let it ruin my day.

Is it common knowledge? I don't remember these threads from last year but maybe I missed them. This seems to be something new they are doing this year. Which is fine, problem is they aren't doing it right. Those hours should have been blocked out prior to people making 60-day FPs for them if that's what they wanted. And what they are doing now (canceling and letting people rebook iirc) is making it worse.

Anyway. As far as the cancer comment, I think we are all very aware that what we are talking about is trivial in the grand scheme of life.

 

[GreatLakes]

Is it common knowledge? I don't remember these threads from last year but maybe I missed them. This seems to be something new they are doing this year. Which is fine, problem is they aren't doing it right. Those hours should have been blocked out prior to people making 60-day FPs for them if that's what they wanted. And what they are doing now (canceling and letting people rebook iirc) is making it worse.

Anyway. As far as the cancer comment, I think we are all very aware that what we are talking about is trivial in the grand scheme of life.

I don't remember them last year either but have seen quite a few this year so I would just not make any reservations past 6:30 personally after seeing the trend reported.

I would wager you that there is a change request in the queue for the availability to be changed so they aren't presented on party nights but these changes aren't instantaneous. It may very well require an architecture change if there is no current party calendar integration even though it seems like it would just need a few lines of code changed.

As for the last comment, you'd think people would recognize the insignificance of a problem like this in the scheme of life but when you see comparisons to arson or adjectives like livid used you realize some people put far too much weight on such little issues.

 

[Kalliope]

I thought it was fairly common knowledge now that Disney cancels FP+ reservations that go past 6:30 on party days. They should update their system so they aren't offered, and I would assume that change is in the queue and will be made shortly, but until then just don't make the reservation to begin with.

I get that it is annoying but not worth getting upset over. It isn't a cancer diagnosis, it is a ride reservation. I wouldn't let it ruin my day.

Common knowledge? Did they do this last year?

 

[GreatLakes]

Common knowledge? Did they do this last year?

No idea. I only know that at this point is has been reported by multiple people that they are cancelling FP+ that have windows opened past 6:30 on party nights so I would just not book any that fit that description and go about my day. I wouldn't rebook them only for them to be cancelled again. YMMV.

I guess I just don't see the point in getting upset about these kinds of things. I just shrug and go about my day.

 

[Kalliope]

No idea. I only know that at this point is has been reported by multiple people that they are cancelling FP+ that have windows opened past 6:30 on party nights so I would just not book any that fit that description and go about my day. I wouldn't rebook them only for them to be cancelled again. YMMV.

Oh, you mean it is supposed to be common knowledge to the minority of visitors that visit this site before their vacation?

 

[JoshuaShaw]

I guess I just don't see the point in getting upset about these kinds of things. I just shrug and go about my day.

I believe the point of getting upset is two-fold.

1.) When complaints are passed on to corporations, they may learn from their mistakes and try to improve their service in the future.
2.) Catharsis.

Hope that helps.

 

[ParrotBill]

Continuing proof that MyMagic+ is sloppy, sloppy, sloppy. The calendar got loaded ages ago, and the FP+ schedule does not get loaded from the same source? Seems clear that ruining the plan for hundreds of people each party day is easier than fixing the system.

 

[GreatLakes]

Continuing proof that MyMagic+ is sloppy, sloppy, sloppy. The calendar got loaded ages ago, and the FP+ schedule does not get loaded from the same source? Seems clear that ruining the plan for hundreds of people each party day is easier than fixing the system.

Some integration aspects of it have indeed been sloppy, including this one. I don't have any inside information about the architecture of MyMagic+'s back end. It is likely that the FP+ and party schedules are not stored together. One is going to be a highly transaction oriented database that needs to be accessible in real time from the user side of the front end while the other is not. If the current code doesn't hook the party schedule it isn't as simple as adding some lines of code to an API call. In that case it is easier to just run a quick query on FP+ reservations that meet a certain criteria and purge them then it is to fix the system.

Once the necessary changes are made (to the architecture, API, code, or a combination of them all) I'm sure that will be the preferred method of dealing with this policy change going forward. Of course it is better to foresee these possibilities ahead of time and have all the necessary data accessible from the system from the start but I've yet to be involved on any project that manages that all or even most of the time. Scope Creep is inevitable as much as we attempt to prevent it.

 

[ArwenMarie]

Sloppy is an understatement from the customer's POV.

 

[grimley1968]

Some integration aspects of it have indeed been sloppy, including this one. I don't have any inside information about the architecture of MyMagic+'s back end. It is likely that the FP+ and party schedules are not stored together. One is going to be a highly transaction oriented database that needs to be accessible in real time from the user side of the front end while the other is not. If the current code doesn't hook the party schedule it isn't as simple as adding some lines of code to an API call. In that case it is easier to just run a quick query on FP+ reservations that meet a certain criteria and purge them then it is to fix the system.

Once the necessary changes are made (to the architecture, API, code, or a combination of them all) I'm sure that will be the preferred method of dealing with this policy change going forward. Of course it is better to foresee these possibilities ahead of time and have all the necessary data accessible from the system from the start but I've yet to be involved on any project that manages that all or even most of the time. Scope Creep is inevitable as much as we attempt to prevent it.

In the case of the bolded, yes I'm sure it was easier from an IT perspective for Disney to cancel those guests' FP's than it was to treat paying guests with respect in the first place. Personally, as a guest, I prefer the "treat guests with respect" approach.

Sloppy is an understatement from the customer's POV.

Agreed.

 

[Ambear]

Some integration aspects of it have indeed been sloppy, including this one. I don't have any inside information about the architecture of MyMagic+'s back end. It is likely that the FP+ and party schedules are not stored together. One is going to be a highly transaction oriented database that needs to be accessible in real time from the user side of the front end while the other is not. If the current code doesn't hook the party schedule it isn't as simple as adding some lines of code to an API call. In that case it is easier to just run a quick query on FP+ reservations that meet a certain criteria and purge them then it is to fix the system.

Once the necessary changes are made (to the architecture, API, code, or a combination of them all) I'm sure that will be the preferred method of dealing with this policy change going forward. Of course it is better to foresee these possibilities ahead of time and have all the necessary data accessible from the system from the start but I've yet to be involved on any project that manages that all or even most of the time. Scope Creep is inevitable as much as we attempt to prevent it.

Forgive me if I'm wrong cause I'm still a bit of a newb... but wouldn't it be even easier to add a couple lines of code to the calendar and FP+ selection tools to not even show those times for those dates? Like a simple if/else statement, an array of times and dates possibly retrieved from a simple database... I mean I could actually think of a bunch of different ways to PREVENT this problem that are very simple, a weeks worth of dev and testing (if that). It's hard to believe disney didn't know the party dates enough in advance to prevent most of these fastpasses from being scheduled.

 

[Angel Ariel]

Forgive me if I'm wrong cause I'm still a bit of a newb... but wouldn't it be even easier to add a couple lines of code to the calendar and FP+ selection tools to not even show those times for those dates? Like a simple if/else statement, an array of times and dates possibly retrieved from a simple database... I mean I could actually think of a bunch of different ways to PREVENT this problem that are very simple, a weeks worth of dev and testing (if that). It's hard to believe disney didn't know the party dates enough in advance to prevent most of these fastpasses from being scheduled.

Haven't MNSSHP tickets been on sale since around May or so? That's well before the 60 day mark for any part day FP+ bookings..

 

[tlmadden73]

It seems simple to me:

If THEY have to cancel your fast passes for ANY reason at ANY time (ride breaks down .. weather .. or a party) .. they should give you a "use any time during the day" fast pass for that day for that ride. They should not just "reschedule" it for you.

In October, Winnie the Pooh was down during my FP+ time. I got a free FP for use ANY time that day for many rides (including Winnie the Pooh, Small World, Peter Pan)

That was a GREAT perk. I would have been upset if they rescheduled me.