To prevent VM sessions that remain logged in we had a template that logs out the user in the end. This worked great with the 2022 versions but we are now moving to the cloud and use the latest (2023.10.4) but the jobs in orchestator keep running untill we stop them. Is there a way to log the user out of the VM and then stop the robot session from running? Even if the logout (using powershell) is the last part in main if keeps running. We want to keep our forced logout to prevent sessions mixing between robots what was big issue in the past.
I’d recommend making a support ticket with UiPath.
The robots should logout when they’re finished with the job automatically.
The robot only logs out if there was no session to begin with. If there was a session it does not logout. That is why we added a logout command at the end of our template to make sure the session is logged out when the robot finishes. Sadly this is causing issues now with the update to the latest version.
The best option is to have a option for the robot to always logout after it finishes even if there was a session already running that was re-used. Sadly this request has never been implemented…
Not really related to solving your issue, but whats the reason for there being a session already active on the VM?
Sometimes a robot stops working and is killed after x time but the VM is not logged out. Maybe some network disconnection or other weird reason related to our companies policy but it happens every week. We tasked all robots with a cleanup for this reason. It worked fine for years.