I have users reporting that they are unable to access Anvil apps at times for the last 2 days. Receiving following error.
“anvil.server.RuntimeUnavailableError: Internal server error: Server runtime failed to start.”
Hi,
So far, there has been no response to @etrimby question, but we are experiencing the same issue, so let me give a bit more information on ours:
Since 29/11/22, we have received at least 17 of these incidents in PagerDuty (we are not aware of the ones that occur on a fresh app load as the code that raises the incident in PagerDuty cannot be loaded due to the error). There is seemingly no rhyme or reason to them, as they can occur pretty much anywhere in our app and are not reproducible, although I’ve encountered the issue myself while developing.
We are using the Python 3.10 (Beta) runtime with the “Standard” environment and some custom dependencies, but the build is successful.
3 Likes
This RuntimeUnavailableError keeps happening to us and is affecting our users, so I would like to know if there’s any actions we can take to mitigate this or whether this is a bug on Anvil’s side.
Is it possible that this could be caused by the server runtime needing time to start up after a period of inactivity while a server callable expects the server to return a result? The only pattern I seem to discern with these errors is that they seem to happen after what I expect are periods of inactivity. After the error happens one or two times, the app is fine again for a while.
was there every a solution or cause determined?
I also experience this. I run a monthly report which results in the same error: anvil.server.RuntimeUnavailableError: Internal server error: Server runtime failed to start.
I have now created a background task that only prints out a message, just to keep the server runtime connected. I hope that this will fix the error.