Robot.Orchestrator_JobFaultedDueToShutdownOrDisconnect - Job faulted due to service shutdown or disconnect

Help Orchestrator
1

Hi All,

One of the bot since 15 days getting faulted intermittently due to reason

{“Code”:“Robot.Orchestrator_JobFaultedDueToShutdownOrDisconnect”,“Title”:“Job faulted due to service shutdown or disconnect.”,“Detail”:“System.Exception: Job faulted due to service shutdown or disconnect.”,“Category”:null,“Status”:null}

This is occured on the non maintainance window and also machine up during this time.

It is not specific to one machine.

Need assistance for this.

Thanks
Pavan

CC: @Anil_G @manasrlenka25

2

Hi @Pavan_Mamadapur1,

Welcome to the community.

Hope this will solve your issue.

Thanks!

3

@Pavan_Mamadapur1

Welcome to the community

Can you check the event viewer logs..that might shed some light

cheers

4

Hi @Pavan_Mamadapur1 ,
This error usually indicates that the UiPath Robot lost communication with Orchestrator or the Robot service was restarted/disconnected while the job was running. Since it is occurring on multiple machines and outside maintenance windows, check:

  • Windows Event Viewer for Robot service restarts, server reboots, or network interruptions.
  • Robot and Orchestrator logs around the failure time.
  • Load balancer, proxy, firewall, or VPN sessions that may be dropping connections.
  • Resource issues such as high CPU, memory, or disk utilization causing the Robot service to become unresponsive.
  • Whether antivirus or security policies are terminating UiPath processes.

As the issue is not machine-specific, focus on infrastructure and network connectivity between Robots and Orchestrator. Correlating Robot logs, Event Viewer logs, and Orchestrator logs at the exact failure timestamp is the best way to identify the root cause.

Thanks

5

@Pavan_Mamadapur1 This error usually happens when the Robot service is restarted/stopped or temporarily loses connection with Orchestrator. The machine can still be up when this happens.

Since it is intermittent and happening on different machines, I would check the Robot logs and Windows Event Viewer at the exact time of failure and verify whether UiPath.Service.Host was restarted or lost connectivity.

Also check for any proxy/firewall/network interruptions between the Robot machines and Orchestrator, and make sure the UiPath Robot service is running continuously.

If the same issue continues across multiple machines, collect the Robot/Event Viewer logs for the failure timestamp and raise it with the infrastructure team or UiPath Support, as this is most likely an environment/connectivity issue rather than a workflow issue.

6

Hi @Pavan_Mamadapur1,

The Robot service on the host may have got interrupted. The common causes could be Windows update or unplanned service restart of the Robot process or RDP session getting disconnected instead of staying non-interactive.

Also, as it is cross-machine, check for a root cause by correlating fault timestamps with Windows Event Viewer (service restarts) + local Robot logs (C:\ProgramData\UiPath\Logs) and also check if sessions are configured to stay non-interactive/unattended and not RDP-locked.

I hope this helps.

Cheers!

7

Hey @Pavan_Mamadapur1

This error means Orchestrator lost its connection to the Robot service mid-job, even though the machine was on.

Here are the top three things to check:

  • Windows Event Viewer: Check the machine logs around the failure time to see if the UiPath robot service (UiPath.Service.Host) crashed or ran out of memory.

  • Network / SignalR Drops: Look for temporary network glitches, VPN blips, or firewall/proxy timeouts that cut off the live connection to Orchestrator.

  • Security Software: Check if your Antivirus or EDR tool is aggressively scanning or momentarily blocking UiPath background processes.