Unattended Job - Log Out Process

[HansG]

Hello,

Can someone enlighten me on the below scenario :

I have just migrated to Cloud platform and i have a VM and 3 robots accounts connected to it.

When i schedule an unattended job, while still connected on the account, the orchestrator command will log me out of the VM while on the rest 2 accounts, when the command is sent, the job is executed live, no log out done. (The UiPath job icon appears in the taskbar). Both jobs are executed successfully.

I would like to have the log out process on all accounts. Grateful if someone can tell me if there is such settings on Orchestrator or if i missed something.

Thank you.

[naveen.s]

@HansG

Give a try like below:

It seems like the behavior you’re describing is specific to the way the Orchestrator handles unattended job execution on different robot accounts. Here are a few points to consider:

1. Session Management: The behavior you’re observing might be related to how session management is configured on the VM and how the robot accounts are set up. Some configurations might automatically disconnect or log out user sessions when certain tasks are executed, such as running unattended jobs.
2. Robot Configuration: Ensure that the robot accounts on your VM are configured correctly in UiPath Orchestrator. Check the robot settings to ensure they are set up as unattended robots and that they are associated with the correct machine.
3. VM Configuration: Review the VM configuration and any session management settings that might be in place. Look for settings related to automatic logouts or disconnects and adjust them if necessary to prevent unwanted logouts during job execution.
4. Logging and Monitoring: Use logging and monitoring tools provided by UiPath Orchestrator to track job execution and any associated actions on the VM. This can help identify any unexpected behavior or issues during job execution.

[Dominic]

Hello @HansG!

The observed behavior is due to difference in the Robot settings (LoginToConsole) in the Orchestrator.

As described in the documentation:

When the LoginToConsole is enabled and set to Yes (i.e Console session)

• If there is an active RDP session when a job is started from Orchestrator, the active RDP session is terminated

When the LoginToConsole is enabled and set to No (i.e RDP session)

• If a job is started from Orchestrator and a RDP session is already active, the process is executed in that session

[HansG]

Hello @Dominic,

That is on-point.

Thank you for sharing the documentation as well.