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

Status
Not open for further replies.
I can tell you our experience. We were there opening weekend, trying on both Saturday and Sunday. We had 6 phones (4 cell, 2 WiFi), all logged into my account. All trying at the same time (though surely our tween and teen fingers were faster than Mom and Dad, ha ha). No one got an error either day. We got BG 14 and then 27 the next day.

I think article implied multiple accounts and not your single account example. There is a specific error message with multiple accounts that can occur.
 
I wouldn't worry about that article. The consensus here and elsewhere is the more trying the better.
Logged in to one account with all tickets linked or logged in to different accounts but all tickets linked? Just not sure if my husband and I should log in to our own Disney accounts or choose one to log in to.
 
Logged in to one account with all tickets linked or logged in to different accounts but all tickets linked? Just not sure if my husband and I should log in to our own Disney accounts or choose one to log in to.
I would pick one account, make sure both tickets are in that account, and both sign into that one account to try for a BG. Make sure that you pick the person’s account that has no other tickets linked to it, so that when you get to the screen to select who you want to join the BG, it will default to only the two of you since you will be the only tickets linked there.
 
Best Wednesday on record to follow the best Tuesday on record. And both the best Wednesdays happened on shortened days...Also, the first time we've had six consecutive days calling 100 or more groups.
473323

It looks like we had an hour of downtime followed by an hour and a half of limping along in stop and go sort of situation before things finally took off and we saw a good 4.5 hours. Then another half hour of downtime and a push to the finish. So 1.5 hours of actual downtime, and maybe another half hour scattered in the stair steps.

They called longer than they did for the 80's night by about an hour, but they started calling almost an hour later as well. As @EmJ notes we kissed the all time high again.

Tomorrow with an early start followed by an early night will be an interesting study. Today's long distribution period may inspire people to go tomorrow, but it will be interesting to see how that is tempered by the Magic Morning Crowd. We haven't broken 100 groups on a Thursday since the first week of operation, so if we can kiss the all time high again it will tell us that some adjustments have been made and that they are at least partially effective.

It is important, though, not to read too much into a single day...but overall the trend continues to improve. It will be interesting to see how we compare to DHS in a few more weeks time.
 
Our trip is coming up in less than two weeks. I thought I had the procedure down until I read this article. I'll copy and paste the part I have a question about.

DO NOT HAVE EVERYONE IN YOUR PARTY TRY SIMULTANEOUSLY
This is the most important tip we can pass along: Do not have everyone in your party smash the "Join Boarding Group" button at the same time. We saw tons of people around us receive error messages doing this and suspect the app gets confused when the same party attempts multiple simultaneous entries.
Instead, designate one person to do the quick tapping and one person to have the app open as a backup, just in case.

I'm surprised by the suggestion to have one person try. Should I assume they mean everyone is using the same sign in info on different phones. If I'm the only one in my group with a Disney account should the rest of my group sign into my account or should they create their own?
This was noted and discussed yesterday. General consensus here is that the author is misinformed/wrong, so don't panic. See the posts below.

They based that on this: “We saw tons of people around us receive error messages doing this and suspect the app gets confused when the same party attempts multiple simultaneous entries.”
I think they’re wrong.
After reading this tread for weeks I to think this reporter is wrong. We have played along at home like many others and never have we got an error message. I guess we will find out next week !!!
Love it when this sort of misinformation spreads so my chances get increased. 😈
This came up yesterday and it was decided that they didn't know what they were talking about.
 
I think article implied multiple accounts and not your single account example. There is a specific error message with multiple accounts that can occur.
Which is why we don't recommend that strategy here -- people here would actually agree with that author about that method not working. We recommend using a single account based on the high success rate reported by DISers. Clearly that author hasn't read this thread!
 
Which is why we don't recommend that strategy here -- people here would actually agree with that author about that method not working. We recommend using a single account based on the high success rate reported by DISers. Clearly that author hasn't read this thread!
I am not sure about this. Mostly people on this thread have said either way is fine.

Anecdotally, I know a number of groups where everyone’s been on their own account and they’ve gotten a BG just fine. My husband and I were only two people, but we were each on our account and we were fine.

I don’t think it matters.
 
I am not sure about this. Mostly people on this thread have said either way is fine.

Anecdotally, I know a number of groups where everyone’s been on their own account and they’ve gotten a BG just fine. My husband and I were only two people, but we were each on our account and we were fine.

I don’t think it matters.
I think it is fine. You might get some oddities if you have different accounts and don't have all of the tickets scanned into some of them, or even the same accounts and you accidentally don't select the same party.

But I suspect that the message you are sending to the server doesn't even have account information, but just ticket information grouped by party. My guess is that when you click Join Boarding Group after verifying the party, the app sends a message to the server that has something like (ticket1,ticket2,ticket3,...)

Naturally, in the first few seconds, these messages stack up and are "spooled". Before they are processed the go through two "gates."

Gate 1 is "Are these people scanned into the park?" If one or more of the tickets in the message isn't scanned in, it kicks back the "Oops, is everybody in the park?" message and prompts you to deselect.

Gate 2 is "Do any of these tickets already have a boarding group assigned?" We know that if the group already has a BG, the user gets the "You are already in a BG" message. I'm not sure what happens when only some of the people have a BG already and others don't. This may be where the trouble is for some folks.

Once through the two gates, the requests go through the BG assignment process, where the ticket numbers are assigned to a group. Once a group has been assigned, the tickets are associated and the success message is sent back.

What is likely, since the two gates are more dependent on other data and not at risk for collisions, is that those two gates are multi-threaded and have multiple processors doing the checks and kicking the errors out if needed.

Once through the gates, it probably single threads to avoid data collisions. It might also multi-thread the BG assignment since even if they go with 10 threads the likelihood of the same group being within 10 messages of each other is low. But considering the simplicity of the logic and the speed of the computers available, I would expect the assignment to be single or possibly dual threaded.

Not that any of this really matters, but knowing how the app probably does its dirty work might assuage some fears of using multiple devices to maximize your chances at a good BG.
 
The next 10 days will be interesting. The first real stretch of extended 15+ hour days.
It should be. At the same time, the attraction essentially operates on a 12-13 hour day regardless of park hours. What will be interesting is if they start letting the attraction board later than they have been.
 
I have been following since day 1 and I know this has been covered, but I didn't think it would apply to me, but things have changed. How can I delete linked annual passes from the app? For the life of me I can't figure it out. Wife and kid are going to sleep in at the hotel and I am going solo. They are ok not riding RoTR this trip.

Also, I know there was a post/article that had all the tips etc. in one place, anyone have the link to that?

Thank you in advance!
 
I have been following since day 1 and I know this has been covered, but I didn't think it would apply to me, but things have changed. How can I delete linked annual passes from the app? For the life of me I can't figure it out. Wife and kid are going to sleep in at the hotel and I am going solo. They are ok not riding RoTR this trip.

Also, I know there was a post/article that had all the tips etc. in one place, anyone have the link to that?

Thank you in advance!
The single article I know of is this one:

https://www.disneytouristblog.com/star-wars-rise-resistance-disneyland-strategy-guide/
And it does not have all the tips. There is no single place I am aware of with all the tips. This thread does, I believe, scattered among almost 5,000 posts. I have bookmarked like 10-12 of the most valuable ones.

:wizard:
 
Status
Not open for further replies.



New Posts










Save Up to 30% on Rooms at Walt Disney World!

Save up to 30% on rooms at select Disney Resorts Collection hotels when you stay 5 consecutive nights or longer in late summer and early fall. Plus, enjoy other savings for shorter stays.This offer is valid for stays most nights from August 1 to October 11, 2025.
CLICK HERE









DIS Facebook DIS youtube DIS Instagram DIS Pinterest

Back
Top