That reminds me. I saw an Instagram blogger (forgot the name), mention "30 or below, or we don't go" lol. So that is probably true for many people. Unless of course you want a later group, which I heard of as well.
Read a bit of the thread
Also of note is that the message does not seem to include any indication of the account the user is signed in to...so this seems to confirm that the system is agnostic to which account you are on and relies on the ticket numbers (guestIds) for the message.I can confirm this. In examining the network activity of the app, I can see that when you tap on the button the join a boarding group from outside the park, the server responds with the list of folks in your party but in that response it states who is in and not in the park.When you continue from the party selection screen, there is no additional network call made, the client just displays the error that people aren’t in the park yet.
Here is the end of the response. I crossed out the 6 guest IDs (my family) because I have no idea how secret those should remain.
View attachment 474850
Unless 140 was the highest issued group today, which doesn't seem like it would be the case. Anyone in the park that can confirm the attraction is down?
Not a bad performance up to that point. 10 hrs without interruption.
Yeah, it looks like there might have been a 20 minute downtime a little after 10am, but other than that seems like it chugged along pretty well today until the 6pm Jawa raid.
That could easily be flushing the queue if there was a large backup. Even so, 20 minutes barely qualifies.
154 now
care to walk any of this back yet?
151 total now
