Closing "The Exit From The Server" Makes Robot To Get Stuck

News Knowledge Base
,
1

Why closing "The Exit From The Server" makes Robot to get stuck?

Sample Environment considered: A queue trigger process is handled by 4 Unattended Robots. Two of the Robots are having issue as they get stuck at the same activity recorded by Robot logs. While other two Robots successfully execute for every item in the queue. It is suspected to be a Robot issue rather than code issue.

To support the statement, run the process from UiPath Robot tray in that server where Robots gets stuck. Verify the working. The only issue observed is when a closure is made using the exit from the server option. Robot that is stuck for a long time when tried to access, randomly and suddenly starts the process to run smoothly .

Investigation Steps: Before starting the job, verify the VM/VDI closure by

  • Signing out from the windows or
  • Clicking on the disconnect or X button or
  • Minimizing the VM in taskbar .

If there is disconnection and running the Robot from Orchestrator, it is recommended to sign out from the machine before running the process.


Disconnecting the VDI may end up in idle Windows session, but for executing the automation process in the machine, UiPath Robot mandatorily needs an Interactive session.



Resolution: To perform any UI Action like click, typeinto etc, the Robot always needs an interactive session to work on.

When the RDP window is minimized or the machine is disconnected using close button or the "The Exit From The Server" is clicked, the interactive session is stopped and Robot gets lost leading to a stuck stage.

  • Ensure to always sign out from the Robot machine, before starting the process in the job Robot machine.