Rise of the Resistance BOARDING GROUPS Superthread Part 1 *No Ride Spoilers Please* *PLEASE READ POSTS 1-4*

[Aurora59]

I want to cry. We are backup group 111.

Used two phones, both Pixel 3a, one T-Mobile, one Google Fi.

We left our hotel, Grand Legacy, at 6:20am, got to security at 6:25am. In line at Line 13 at 6:27am, line was almost to monorail.

7:03am line was almost at DCA.

7:06am gates open, 7:09am they started letting in, 7:11am we were in!

I don't know what happened, we both kept getting a red bar that it was full. Finally my husband got the back up.

Cheers everywhere made it so much worse.

I'm super worried since yesterday only got to low 90s.

FYI, Gates 13-16 didn't split before we got in.

So sorry! Hopefully it will be a good ride day & more groups will be called today.

 

[DLRExpert]

Going to head over there tomorrow morning with the hope of getting a late BG.
What is your best guess at the time I should try and get the BG at.

Normally I book it right away, this time I figure give it 45 seconds, but wondering what someone else may recommend.

118 hopefully they have a good day. It was pulled at 8:01 mark

 

[Katniss Mellark]

I was playing from home today, and I received a different error message for the first time. It’s a red message saying “not admitting new guests. The experience is currently closed to guests not already in a boarding group.” This was a few seconds after 8 before backup groups even started. I had already gone through the whole process once with no issue, and then this message came up. Do you guys sometimes get this message too? I don’t remember this one before.

 

[Aurora0427]

I want to cry. We are backup group 111.

Used two phones, both Pixel 3a, one T-Mobile, one Google Fi.

We left our hotel, Grand Legacy, at 6:20am, got to security at 6:25am. In line at Line 13 at 6:27am, line was almost to monorail.

7:03am line was almost at DCA.

7:06am gates open, 7:09am they started letting in, 7:11am we were in!

I don't know what happened, we both kept getting a red bar that it was full. Finally my husband got the back up.

Cheers everywhere made it so much worse.

I'm super worried since yesterday only got to low 90s.

FYI, Gates 13-16 didn't split before we got in.

I’m so sorry. Hoping the ride is on its best behavior for you today.

 

[brightlined]

We pulled BG 44 this morning. Anyone have a guess what time that # usually gets called around? I’m worried because our group’s Itinerary is set and I can’t change it. So if it happens between 11 and 12:30 we are screwed.

If things are running optimally, you'll probably be called during that period, if not a little before. (But that's if things are running optimally.)

But, even in that case, I think you'll be fine. As long as you can plan to do it at 12:30, your 2-hour window should be good to go. And even if you're a little late getting back, I don't think they're turning people away, especially if you explain what happened.

 

[Aurora59]

SIAP...how soon can you get/test MaxPass in order to see if your RoTR strategy is going to work? Let's say official park open is 8 a.m. local time and I scan into park at say, 7:15...do I have to wait until 8 am. to test grap a FP?

You can get a Fast Pass immediately after you/your group has scanned in. No need to wait till park opens.

 

[durantigger]

I was playing from home today, and I received a different error message for the first time. It’s a red message saying “not admitting new guests. The experience is currently closed to guests not already in a boarding group.” This was a few seconds after 8 before backup groups even started. I had already gone through the whole process once with no issue, and then this message came up. Do you guys sometimes get this message too? I don’t remember this one before.

That's what we were getting before finally getting a backup. Got it immediately.

 

[brightlined]

I was playing from home today, and I received a different error message for the first time. It’s a red message saying “not admitting new guests. The experience is currently closed to guests not already in a boarding group.” This was a few seconds after 8 before backup groups even started. I had already gone through the whole process once with no issue, and then this message came up. Do you guys sometimes get this message too? I don’t remember this one before.

Did you hit the ROTR page (click on Find Out More) at all before 8am? I'm suspicious that this is a new error display, but that it's getting triggered by that page getting cached (with "closed" information).

 

[StarGirl11]

@durantigger Ugh so sorry to hear about your guys problems.

Only bright side of a late BG means it takes away the stress of the doctors to Disney probably

 

[durantigger]

Did you hit the ROTR page (click on Find Out More) at all before 8am? I'm suspicious that this is a new error display, but that it's getting triggered by that page getting cached (with "closed" information).

Nope. And did atomic clock countdown. I seriously think I did everything "right."

 

[baozi]

I did pretty well before but had problems today.
The lower cutoff number for backup group, and the fact that they haven't called for any groups may indicate that there are some known issues...

Nope. And did atomic clock countdown. I seriously think I did everything "right."

 

[StarGirl11]

I did pretty well before but had problems today.
The lower cutoff number for backup group, and the fact that they haven't called for any groups may indicate that there are some known issues...

I wouldn’t call it a lower BG until we know for sure what they’re starting at. DL does start at 1 or 2 occasionally so it could still be the usual 70 regular

 

[Skyegirl1999]

Did you hit the ROTR page (click on Find Out More) at all before 8am? I'm suspicious that this is a new error display, but that it's getting triggered by that page getting cached (with "closed" information).

People are posting screenshots of it on social media. Seems to be new. I wonder if the addition of that message messed up the app a bit and led to some issues?

It sounds like we have several reports of unfortunate glitches and errors this morning. Just a reminder that these are not necessarily user error, and even if you do everything “right,” this can still happen. As I’ve said before, it’s great that most people on this thread have gotten good BGs by following the strategies here... but keeping the unpredictability in mind can help with both managing expectations and assigning “blame” for people who missed out on a good BG. I really don’t think that’s fair to them.

I hope ROTR has a great day today and that everyone gets to ride.

 

[StarGirl11]

i'm surprised they're letting people race over there..i saw a video of people running for those kiosks...i thought the CMs don't allow rope drop running anymore..

They’e not supposed to. That didn’t stop a bunch of people taking off around the hub towards FL right after them announcing don’t run over the messages after they dropped the rope 5 minutes before official park opening

 

[coaches24]

our BG story is this. We got to harbor side security at 7:30. Through security and gate 29 into park by 7:50. At 8 we were in line outside SM. I opened app at 7:59 and at exactly 8 I hit the join boarding group button and got nothing. So then I quickly hit my status and join boarding group and got BG 44. Lady and her DD right in front of me got 29 1 second before me.

 

[Katniss Mellark]

Did you hit the ROTR page (click on Find Out More) at all before 8am? I'm suspicious that this is a new error display, but that it's getting triggered by that page getting cached (with "closed" information).

Today yes. I have been having issues with my Find Out More button turning red. So I experimented today by being in the Find Out More page first, then clicking My Status at 8. This worked the first time, no problem. When I backed out to try again, I got the red error message.

 

[handyl03]

BG 28 today! Have they even started boarding yet? My app doesn’t show any boarding groups.

 

[brightlined]

People are posting screenshots of it on social media. Seems to be new. I wonder if the addition of that message messed up the app a bit and led to some issues?

As a software developer, I can't imagine having to launch a change like this, knowing that it would be nearly impossible to test real-world conditions - and that a missed error would mean ruining people's day.

I'm trying to figure out the situation that this error message was trying to accommodate, because it doesn't really seem like it helps anything. Given that they haven't opened the ride yet, I'm wondering if they initially set a very low number of BGs for today, and the cap got hit immediately, throwing this error. That would leave the possibility that this error gets thrown when backups run out, which would explain why we wouldn't have seen it before - normally we don't know that backups are done until a while afterward.

 

[StarGirl11]

Still not boarding

 

[Mappyland]

Nope. And did atomic clock countdown. I seriously think I did everything "right."

I have played from home a few times too, I got this yesterday, had to relaunch the app.

Today I had no issue.