We are running Atlas with WebAPI as a "cloud function". Hence, when the service is requested, it may take a bit of time for it to respond during startup. Currently, Atlas doesn't wait much longer or provide a loading page, what the user sees is...
Application initialization failed
Unable to connect to an instance of the WebAPI.
Please contact your administrator to resolve this issue.
Waiting a few seconds and refreshing solves the problem. However, this is a user experience problem for us. What we'd like to have is a configurable splash screen plus a longer timeout before an error is shown.
We've not tested, but there could also be similar challenges where the cloud function unloads during longer periods of being idle.
We are running Atlas with WebAPI as a "cloud function". Hence, when the service is requested, it may take a bit of time for it to respond during startup. Currently, Atlas doesn't wait much longer or provide a loading page, what the user sees is...
Waiting a few seconds and refreshing solves the problem. However, this is a user experience problem for us. What we'd like to have is a configurable splash screen plus a longer timeout before an error is shown.
We've not tested, but there could also be similar challenges where the cloud function unloads during longer periods of being idle.