I have the following question.
Sometimes the machine I have set as unattended will be automatically unlocked.
But at other times the machine is not unlocked, although the processes are executed correctly.
Would I like to understand why?
For an Unattended Robot, the Windows machine does not necessarily need to remain visibly unlocked for the process to execute successfully.
If the process runs correctly while the machine appears locked, that is expected behavior. UiPath can establish the required Windows session in the background based on the Robot/Runtime configuration.
If the machine sometimes becomes unlocked, it can be related to the Windows session state, Robot settings, machine configuration, or how the Robot connects to the machine.
I would recommend checking the Robot/Windows configuration and reviewing the Robot execution logs and Windows Event Viewer around the time the machine gets unlocked.
Hope this helps!
Can you please elaborate
one thing I see is when you keep the machine logged in and only disconnect it then it would not be logged out generally…but when you heeep the machine logged out and robot logsin then it would logout automatically
cheers
I assume this could be the reason because this is how an RDP session works.
If the machine already has an active/disconnected session (not fully locked but not logged off either) from a previous run or leftover RDP connection, the Robot doesn’t attempt an unlock because it doesn’t see a lock screen to unlock. It just reuses the existing session. This is the most common reason it “sometimes doesn’t unlock”, because there was nothing to unlock.
Cheers!