I’ve seen that this problem can be resolved (or greatly mitigated) by setting the loginToConsole value to false in the UiPath.Settings file on the robot. You will need to be a local administrator on the robot to change this setting.
Chris
yes. I have execute process ‘XML mapping’ in uipath studio, on that time my computer gets log off. if i execute some other process in uipath studio. This issue not happend.
You should be admin on your machine (where uipath studio is installed) and have access to change the file “UiPath.settings”, changing the key “LoginToConsole” to false. Save the file and execute again your job at Orchestrator.
This issue will happen when you are signed in to remote desktop from your or some other user id. Try signing out all the logged in users and try running your process again. This worked for me.
I know its an old issue. But i still encountered it this today.
The flow runs fine when launching it from studio or from the robot manually, but you get a “desktop disconnected” error when launching it from Orchestrator.
In my case the problem was a “SEND HOTKEY” activity with an “ENTER”. I did not use indicate the element and this caused the RDP to close instead of just typing the enter where it typed its last action.
Solved it by using “indicate on screen” on all the items pointing to the correct window.