Hello,
Thank you for posting in Microsoft Q&A.
Based on the description, I understand your question is related to Azure Automation runbooks stuck in the queue while others work fine.
Monitor the resource usage of your Automation account to ensure it is not hitting any limits.
Runbooks may remain queued if the resources on the Automation worker are unavailable. Check that there are enough resources available. You might need to scale up your Automation account or use a Hybrid Runbook Worker.
Incorrect configuration can also cause issues, check your runbook script executes successfully on your local machine to identify any potential issues.
High volume of requests can lead to job throttling, causing runbooks to queue. Try to distribute your runbook executions more evenly over time to avoid throttling.
Have a nice day.
Best Regards,
Molly
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it