Issue :
Robot is UNRESPONSIVE
Troubleshoot approach:
Please implement the below approach sequentially
Approach 1: (To verify if the particular Robot which is Unresponsive is responsive now & shows the heartbeat)
- Restart the Robot service. ( WIN + R ) RUN -> Services.msc -> UiPath Robot -> Restart.
- if possible reboot the particular Robot machine.
Now verify the behavior of the particular Robot in Orchestrator
Approach 2 : (To verify if the particular Robot which is Unresponsive is responsive now & shows the heartbeat)
(Re-provision the Robot again )
Steps:
- Disconnect the Robot.
- Delete the Robot from Orchestrator.
- Restart the Robot service.
- Re-provision the Robot in the Orchestrator first and then connect the Robot from the server.
When we re-provision the robot, the settings file is updated. When the job is triggered it downloads the latest settings of the robot and execute
Now verify the behavior of the particular Robot in Orchestrator
Note:
If the above approach give positive results, kindly follow the same for the remaining Robots those are Unresponsive , disconnected
If there is no positive results from the above approach & if restarting the entire Orchestrator is a viable option at your end than follow the approach 3.
Restart of Orchestrator to be followed if no process is currently running & no jobs are affected
Approach 3 : (Restart of the Orchestrator)
Step 1 :
Navigate : IIS -> Application Pool -> You application Pool Name -> Recycling (Right Side Panel option) -> Next -> Finish
Step 2:
Navigate : IIS -> Website -> Restart the Website
Now verify the Robot heartbeat in Orchestrator.
In case if this is a repetitive and frequent issue, kindly verify the database space availability & the records count of the table in the database.
If count more than 2 million, implement database maintenance (same detailed in the below link)