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
We were doing some maintenance last week that required a brief interruption to MySQL database access (i.e., for cached transit data and user account info), and when the database came down briefly, anyone who had OneBusAway opened in their browser to a screen showing arrival estimates saw this error:
We should create a more user-friendly experience during a database interruption by showing a more understandable message to the user, and also keep them on the arrival estimates screen so that a refresh will be automatically attempted again after a certain time (at which time database access may be available again, which would automatically clear the error message). In the current design, the HTTP 500 error kicks the user off the page and the page won't automatically be refreshed, which means the user has to manually refresh to get back to the normal screen, even if database connectivity was already restored.
The text was updated successfully, but these errors were encountered:
We were doing some maintenance last week that required a brief interruption to MySQL database access (i.e., for cached transit data and user account info), and when the database came down briefly, anyone who had OneBusAway opened in their browser to a screen showing arrival estimates saw this error:
We should create a more user-friendly experience during a database interruption by showing a more understandable message to the user, and also keep them on the arrival estimates screen so that a refresh will be automatically attempted again after a certain time (at which time database access may be available again, which would automatically clear the error message). In the current design, the
HTTP 500
error kicks the user off the page and the page won't automatically be refreshed, which means the user has to manually refresh to get back to the normal screen, even if database connectivity was already restored.The text was updated successfully, but these errors were encountered: