Our systems team has identified the root cause of the issue to have been scheduled maintenance on the databases, which interrupted the services for long enough that the services were not able to successfully recover automatically. The database updates themselves were not interrupted, and the databases are healthy. We are currently also integrating a more resilient configuration for these services to ensure that this does not happen again. If you continue to see issues with your background jobs after the posting of this update, please open a ticket with us and let us know.
