UX will not login if a server is "starting"

If a user signs into UX and a data instance is unavailable (wrong port or just not running), UX handles it correctly and allows the user to login but shows an error when trying to access content related to that instance.

However, if a user was to login and that same server was starting up (important for servers with long start up times), the user would be stock on a blank screen.

It seems that UX does not handle the 503 Service Unavailable response from a server that is starting. 503 should be treated the same way any other failed connection is handled. Even better, would an error that indicates the server is still starting.

Note: This is important because we have archive servers that are routinely taken offline for updates, these servers are connected to UX to support historical reporting. However, when they are restarted for maintenance reasons it blocks users from accessing production UX.

Comments (4)