Just a quick FYI on a new Knowledge Base article we published today. This one talks about an issue where the Runbook Service takes itself offline due to database errors resulting from being the victim of one or more deadlocks. Orchestrator platform events as viewed in the Runbook Designer or the Orchestration Console reports the following events:
Summary: Runbook Server <computer> is experiencing frequent errors while accessing the database
Details: The Runbook Server is experiencing frequent errors while accessing the database. Verify the status of the database server. If the problem persists, contact Technical Support.
You can get all of the details in the article below: