Robot gets disconnected after Logging Out From the System

[Shashi123 (Shashi)]

Hi team,

I am trying to run the bot in unattended mode. When I am logged inside the machine and run the job from orchestrator it runs successfully. The moment I log out of the machine and than try to run the job I dont get the machine name in the machine name option of jobs page.

And when I check the robot status there also robot status is disconnected.

Thanks

[Gokul001 (Gokul Balaji)]

Hi @Shashi123

Do you have Unattended License

If yes, Check the Service Host is required

1. 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 unattended automation.
2. Make sure that you assigned un attended bot license for the Bot(VM) which you are trying to run your process un attended.

Have a look on the thread

Unattended but working only when the screen is open

Thanks a lot @seanrockvz13 for explaining to me about many things. After checking the whole system setting again . I have come to know that the path is installed with the Robot type as User Mode in the non-working VM . After the reinstallation is done with the robot type as Service Mode the VM is working fine. [image] If anyone faces the same issue you need to check this first in task manager->Details [image] There should be a Service. host available in the running state for unattended and…

Regards
Gokul

[postwick (Paul)]

Stop logging into your unattended servers. This interferes with the automation. I bet you didn’t log out, either, you just disconnected. So go log back in, then SIGN OUT completely, from the start menu - don’t just close the RDP window. Now run your job.