Looking at the data after I got home, I don't think it was the app.
I think we saw numerous issues today with the app, but I don't think it *caused* the downtime, but was more a symptom of the downtime.
BG 58 was called at 1:26:40, and the app (and signs) seemed to go to the "boarding has concluded" statement at exactly... 3:26:40.
So it seems like there is a default in the VQ system, where if all groups are called it resets everything to zero and displays the "boarding has concluded" statement on the signs around the land. You can see this as the queue drops to 0 start and 0 end, then they fix it about 10 minutes later at 3:37:16. They then reset the queue multiple times (each time adding additional return time, but it apparently didn't work the way they wanted it to).
This tells me multiple things about their boarding system though.
- It's fully automated to "close" when all groups have been called.
- The return time is set when the boarding group is first called.
- The return time is fully automated and basically an offset to the call time, and that offset time is stored.
View attachment 448001