orchestrator 2022 runbook orphans

Thanks will check events, etc next time we get orphaned runbooks to see if db related events appear.  

SQL deadlocks are a plausible lead for your intermittent orphaned runbooks, but UR1 and the orphaned status alone do not identify the cause. Microsoft documents an Orchestrator issue where concurrent runbook completions deadlock and the runbook server goes offline.

Start by matching an affected runbook’s timestamp with the Events tab in Runbook Designer and the server’s trace logs. Look specifically for frequent database-access errors, then ask your DBA for the corresponding SQL deadlock graph. Microsoft’s documented signature involves dbo.sp_UnpublishPolicyRequest and dbo.POLICY_REQUEST_ACTION_SERVERS.

If that signature matches, have the DBA check whether the SeqNumber index described in KB2860832 exists and apply the documented resolution through your normal database change process. Do not assume every orphan needs that index. If the signature differs, retain the job IDs, server names, SQL version, and traces for Support before making database changes.