I would love to here how you manage to keep your bots working fine on a daily basis. We have a discussion if we need a bot controller or we are able to keep control over our bots by developers having rota every week. We use Orchestrator and specific SQL queries to check all the failures/ pending items. I have impression that if you have more than 10 robots (licenses) it is becoming tricky to control using only Orchestrator. I would love to see how you tackle it!!! Thanks a lot in advance for your opinion/ comments!
We already have over 60 software robots in my organization and we rely on the UiPath Orchestrator.
The basis for the stable operation of robots is to build processes into a framework with efficient error handling and process recovery.
Once I built an API robot that checks the so-called heart-beat the robots of other robots and verified if they were working if so, if they were working on things or if they crashed. The robot has finally been shutdown because the robots use now a better framework.
You can use SMS / e-mail notifications, but this is more in the case of Risk SLA processes.
Managing 60 robots on the Orchestrator is quite a challenge because you have to maintain the Orchestrator database.
We have to delete logs from the database and processed transactions on an ongoing basis. Daily database service is provided by the IT department.
It is also good practice to define the timeout for the process (the maximum processing time for a single case) and to program it into the framework.
In my company we have hundreds of robots with as many processes dispatched on 3 orchestrators. We were first using Orchestrator and ElasticSearch / Kibana to monitor our bots but we found out that it was not sufficient to be alerted when something went wrong. So I decided to create an application so called UiPath Watcher that is a web interface helping monitor robots by triggering alerts based on rules like « raise an alert if a job is lasting more than 30 mn ».
I’m going to publish the solution in UiPath Connect Marketplace soon, I’ll let you know!