Unable To See Logs In Orchestrator For A Single Robot, All Other Robots Write Logs As Expected

All other Robots are writing logs to Orchestrator but one Robot stopped writing logs a week ago. How to fix logs not showing up on Orchestrator for the particular Robot?

Issue Description: All other Robots are writing logs to Orchestrator but one Robot has stopped writing logs a week ago. How to fix logs not showing up on Orchestrator for the particular Robot?

Root Cause: Likely, one of the temporary storage files is corrupted and needs to be recreated.


Resolution:

  1. Close the Robot Tray and stop the Robot service on the affected robot machine. To stop the robot service,
  • Open a "Run" window and type the command services.msc
image.png
  • Look for "UiPath Robot", right click and click "Stop"
image.png

  1. If the Robot is installed on
  • a 64-bit machine, navigate to "C:\Windows\SysWOW64\config\systemprofile\AppData\Local\UiPath\Logs"
  • a 32-bit machine, navigate to "C:\Windows\System32\config\systemprofile\AppData\Local\UiPath\Logs"
  1. Delete any files within this folder. The Robot uses this folder to temporarily store logs before pushing them to Orchestrator.
  1. Restart the Robot Service and Robot tray and execute a job from Orchestrator.

Refer to the document How Robot Pushes Log To Orchestrator .