If the server crashes that Orchestrator sits on, is there a way to either:
- Have the Orchestrator and running Jobs restart automatically?
- Get an alert that the Orchestrator server crashed?
Basically, we have an unattended automation that we need to run continuously and so need recovery options if the Orchestrator server crashes…
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Watch the videos on our official YouTube channel for more visual tutorials.
Meet us and our users on our Community Slack and ask your question there.
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
Cheers from your friendly
No one has an answer to this?
By default IIS will have Rapid-Fail Protection enabled and will restart the pool a maximum of 4 times (5 Errors) if those errors occur within a 5 minute period of each other.
If that is occurring, you’d want to figure out why as well as think about multiple Orchestrator instances for High Availability / Disaster Recovery.
I am not aware of a mechanism out of box to start missed triggers due to a crash. I know if you place Orchestrator into Maintenance Mode it will not restart missed triggers however for each tenant you can review the logs for maintenance and it will indicate which triggers were missed.
How quickly you want to identify the server failure will determine what type of solution you would want but generally speaking you’ll want some script or monitoring tool/application to monitor your resources/logs and act accordingly whether that is to restart the services, or send an alert of sorts.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.