I think I would assume that the app does automatically refresh at some interval, but I know if I’m looking at wait times “right now” I would definitely pull down to refresh.
I think this is pretty clear when the wait time is being calculated (last updated):
When this is posted on lines, everyone is fairly quick to respond. We try to be sympathetic and encouraging, and I feel like we always suggest they need to refresh however I never considered they might be using a printed plan. I do wonder if some users do not create a plan (that would be me a lot of the time now) but simply look at the park they are in and pick an attraction from the wait times they see. Would make sense if they are not refreshing each time that there’s a discrepancy. I’ve always “pulled” the app down and refreshed but if I remember correctly it was a bit more obvious to refresh in the older app format.
I use Lines above all as a planning tool, to see in advance what is feasible, and I very rarely refresh my plan (or check wait times in the app) while in the parks. I may refer back to my plans while in the park though (which feels almost equivalent to using a printed out copy of the plan), and indeed sometimes I notice discrepancies between the plan and how the actual experience panned out.
if I had to answer your question, I would assume that there’s some level of automatic refresh (but also if I really wanted to check something specific I’d probably intuitively pull down for a refresh of times). I think the reason I would expect that there might be an automatic refresh is that i usually also have MDE open while touring to check wait times, and those seem to update automatically? Hope that makes sense.
Bit of both. Opening the “page” has it refresh immediately. Pulling down on the page also refreshes it (though i feel sometimes it locks into last-known cache at times)
And it automatically updates itself every 10 minutes.
So for 100% up to the date accuracy, I completely close down the app and reopen. Normally, I exit out to the “day” and the refresh, and then go into the specific park.
I think there have been issues recently with app users relying on the info on the homepage of the app and it has not updated. I know someone was angry that the AK were not correct, but it was a refresh issue.
@youcanfly mentioned that at times users post to chat and liners offer help but ask the poster to contact TP through the link on the homepage. Is there something else we should do?
The last specific post I remember was a demand for a refund since their wait was 30 minutes longer than the time TP said. Clarifying questions such as: are you referring to the “expected wait” in the app or your touring plan, did you optimize a plan, was your wait lower than the posted time? Were all unanswered.
I tend to assume that Lines is working off historical data, so things like a ride going down probably is incorporated into the estimate but will lag? If you get into a line estimated at 20 minutes but then the ride goes down for an hour (or there are multiple unanticipated stops, etc) then I’m not sure how Lines would handle that.
(Now I’m interested in learning more about the intraday adjustments!)
I always assumed that I would need to check things off / rerun things if I wanted up to date info.
For me specifically in the past, I usually was in BG1 and just swapped over to Lines every once in a while to check waits. I would hope that swapping in and out of the app would get updated times (does it, versus reopening / refreshing?) but the “last updated” line works for me.
Yeah, this is the most recent example, and what spurred this post.
We’re grabbing data from Disney every 2-4 minutes, so with updates and batch processing times we should be updating our own estimates every ~5 to 10 minutes at the outside.
Given those refresh times, it should be unusal for us to be off by 30 minutes when displaying a posted wait time. That would mean Disney’s posted wait time changed by 30 minutes within the last ~10 minutes.
I’m sure it happens, but it shouldn’t happen often. Which is why I’m trying to figure out other possible causes.
I optimise after each attraction in the plan has been completed. Thereafter, I assume that each time I open the app it would refresh the live wait times.
If the the ‘wait times last updated’ time is more than 10 mins old I’ll pull to refresh.
I feel like that poster was describing a TP expected wait and not a posted wait. But I don’t know for sure.
I have had TP expected waits be off significantly before (a specific MFSR wait comes to mind) and it’s very frustrating when you are “trusting” the system. Obviously I know that things happen but I think that new people with high expectations can be tough critics.
I feel like someone who would post this has unreasonable expectations of what a forecast can provide. Would they do the same if their weather app told them there would be sunshine and it rained instead? Would they leave their umbrella home if they saw storm clouds with their own eyes, even if the app said 0% chance of precipitation?
That said, I appreciate that Len is taking the complaint seriously and trying to improve the product.
