Cannot bring the target application in foreground because the Windows session is locked

[serdarkavrazli (Serdar Kavrazlı)]

I have a remote server. The UIPAth assistant is located here. Robots that will not be used for my remote server this will be used
“Cannot bring the target application in foreground because the Windows session is locked.”

[Gokul_Jayakumar (Gokul Jai)]

Hello @serdarkavrazli
Kindly refer this, you may got some idea

Unattended bot gets disconnected when the system is locked

Hi, Can anyone help me on how to run an automation when your system where the robot is placed is locked? I have created an unattended robot and give my domain and username and credentials while creating it. So i have locked my system and try to run the bot using cloud orchestrator from another machine it does not work and the bot gets disconnected. But as soon as I log in the execution starts automatically. Any clue why this may be happening? Tried from my mobile as well and it gives me th…

[Gokul001 (Gokul Balaji)]

Hi @serdarkavrazli

Can you check your UiPath run as service mode?
We can check it if UiPath.Service.Host.exe is running or not in Task Manager of OS.

Bot not running in unattended when logged out

Hi @Pushpanagraj_Nag Could you please check below things first. We should have any on going connections with the VM(bot machine) like user logins. to avoid this we have to restart the VM to make sure that no user logged into this VM machine. Have you installed the Bot which you are running as un attended from orchestrator by using MSI installer since we must install the bot with service mode since service mode bot is required for un attended automation. Make sure that you assigned un attended…

Regards
Gokul

[postwick (Paul)]

Assistant has nothing to do with unattended automations.

Manually log into the server via RDP, using the same account(s) as the robot, and then SIGN OUT completely from the start menu. Do not just close the RDP window. This leaves the session active but in a state similar to being locked, and interferes with jobs.

In general, it is best practice that humans do not log into your automation server(s). If they do for some reason (testing, troubleshooting, etc) they must LOG OUT completely, not just close the RDP window.