You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After refresh cycling to test the SMS app, Ryan noticed that the bus went from expecting to be 10 minutes late to an hour late. But he observed that the bus that came was not an hour late.
Is it possible that after the expected arrival time for stop, the SMS app looks at the next trip and doesn't look at the existing late trip. Sorry for word soup. Did that make sense as a possible reason?
The text was updated successfully, but these errors were encountered:
I have noticed something similar before, but I think it is from Bustracker. If you refresh the text version of Bustracker and the bus is really late it starts showing you the next scheduled arrival time instead of the very late ETA. I'll check on this.
I talked with Ryan with People Mover and he wanted to pass on a bug report.
Monday Jan. 4th, 2015 8:07 am
Route 75 outbound
Stop 0004
After refresh cycling to test the SMS app, Ryan noticed that the bus went from expecting to be 10 minutes late to an hour late. But he observed that the bus that came was not an hour late.
Is it possible that after the expected arrival time for stop, the SMS app looks at the next trip and doesn't look at the existing late trip. Sorry for word soup. Did that make sense as a possible reason?
The text was updated successfully, but these errors were encountered: