Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Admin Console handling of server unavailable (e.g. over restart) #3663

Open
amcclain opened this issue May 15, 2024 · 0 comments
Open
Labels

Comments

@amcclain
Copy link
Member

amcclain commented May 15, 2024

If you are browsing the Admin Console and lose your connection to the server - e.g. across a restart - the current handling is extremely scattershot. Each tab or sub-tab fails in its own way, with a combination of modal alerts, inline error messages, and missing / mysterious exception handling.

For the admin console in particular, it would be great to have a more unified sense of "am I connected to the server in general?", managed more centrally, perhaps via a combination of websocket connection status with a fallback heartbeat / connectivity check of some kind (as websockets won't aways be enabled).

If the server is detected to be unavailable, we should show a clear alert that's visible across the entire admin app. Could consider if the app should remain browsable, in case you have some data already loaded, but I'm not too sure that would work out in practice, as many tabs blank out their data (again in an inconsistent way). Might be better to replace the entire app with a placeholder indicating what's going on. Could even have a little countdown timer to the next liveness check or something cute like that.

I believe this would be some nice polish to the admin app - which is exactly the kind of app where you want to know really clearly and immediately if you've lost connectivity - and also provide an example strategy business apps could use themselves, if warranted.

@amcclain amcclain added the admin label May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant