Robot is disconnected

Help Robot
,
1

Hi,

We receive alerts from Insights whenever a Robot get disconnect and we were using AWS workpsace as VM’s for Robots. So, this alert mesage we receive randomly and wanted to know if there will be any impact on Job. For that we monitored and identified one of the case that when we received that alert that Robot got disconnected also received below error from a job which triggered on same Robot after 4 minutes we received alert.

could not start executor. creating user session timed out error

So could you please let us know why this Robot is disconnecting and suggest solution to fix this issue?

Thanks!

2

Hi @Rama_Thota

There can be one of the various reasons:

1)when the UiPath Robot service is stopped,
2)when the robot is manually disconnected through the UiPath Assistant or Orchestrator, 3)or when the session times out.
4)Additionally, if the robot is unresponsive (e.g., it fails to send heartbeats to Orchestrator for a specified duration), it will be marked as disconnected.
5)or if it encounters an error during execution, it may also be disconnected.

My take - 4th scenario might be what happened in your case unless there was a job running using that robot before triggering another job.

3

@Rama_Thota

  1. Is there any maintainance cycle goign on vms?
  2. Mostly its the robot hearbeat issue.typically it sends a ping for every interval and that is how orchestrator knows that the machine is available
  3. Also if a user session is already present then also you can see this error.this typically occurs when someone is already logged in the system

Cheers

4

@Rama_Thota - If you have the VM access, try to restart it