If you have many runbook instances that complete at the same time, you might end up with a lot of deadlock errors in the runbookservice log.
These deadlock can also make the runbook jobs fail with the error: Interrupted by user or runbook server
This can be caused by a missing index on the POLICY_REQUEST_ACTION_SERVERS table.
This is described in: https://docs.microsoft.com/en-us/troubleshoot/system-center/orchestrator/runbook-server-goes-offline
The KB above referes to Orchestrator 2012, but I’ve noticed that the index is missing in a brand new 2019 installation aswell.
Add the index with the following T-SQL:
CREATE NONCLUSTERED INDEX [IX_POLICY_REQUEST_ACTION_SERVERS_SeqNumber] ON [dbo].[POLICY_REQUEST_ACTION_SERVERS] ( [SeqNumber] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
Now you should end up with a total of two indexes on the table.
