Hi anonymous user,
Welcome to Microsoft Q&A! Thanks for posting the question.
Apologies for the delayed response. The runbook can restart due to several reasons and some of the common reasons are available below:
- Fair share limitation, depending on the type of runbook. If you are running into this issue, it is recommended to use "Hybrid Runbook Worker".
- The sandbox executing this job reached its limitation, which is available here.
- The job execution crashed due to unhandled exception/error (which might even be transient or short lived).
Here are some of the recommendations that would help you investigate the error and design the Automation solution to overcome such issues:
- Please evaluate the solution with respect to involved task and chose the recommended Runbook Execution Environment as available in table here.
- Whenever you see the runbook job getting failed/restarted, please review the "Job Status" to gain more insights of the failure.
- Examine the activity logs in for the Automation account to get more details of such failure/restarts.
- This link has some of the recommended measures to follow, to get a resilient automation workflow.
- Refer to this link for additional guidance on troubleshooting runbook issues. In case you are still facing issues with your runbook, you may also contact us with the details as available here.
Please let me know if you have any questions.
---
Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.