Has anyone seen any performance or non-fatal errors stop runbook processes when using Get-AzAutomationJob, Get-CurrentRunbookName or related cmdlets?
We are having runbook jobs hang indefinitely but randomly because of an issue likely with Get-AzAutomationJob returning and “endless” stream of Jobs.