Fresh Database Connections After a Pause
After a quiet period our servers now open fresh database connections before the first request, so saving changes no longer fails on a connection the database had closed.
#What's Changed
- [Fix] The first change saved after a few quiet minutes, such as signing in, saving a key or posting an incident update, could fail because the database had closed the connection in the meantime. Connections idle for more than 4 minutes are now replaced before the next request uses them.