Skip to main content

I am having an issue with unattended automation where if the bot starts and the session is locked, it is unable to unlock the session for use. I get blank screenshots and GUI interactions fail. Deployment type is Single User RDP.

The test bot I have runs “query user” on a python script and emails me the results with a screenshot. It always shows active so I know it’s not a disconnected session, and the screenshot tells me if it’s unlocked or locked by if it’s blank or not. 

If there is no session, the bot runner can log in and the bot works.

If the session is already unlocked it works.

But if the session is locked it cannot unlock it.

Hi ​@jduncan ,


Since you are getting Black screen, it is clear that the RDP session is not properly getting logged-out. Please refer the below thread and see if it helps or not.

 

Bots Failing to Locate Elements Unattended Mode — Black Screenshots Captured | Community


@Padmakumar I’m not trying to log out, I’m trying to lock the session when the bot is done but it’s not unlocking when I run the next bot. 


@Padmakumar I’m not trying to log out, I’m trying to lock the session when the bot is done but it’s not unlocking when I run the next bot. 

 

That is not an ideal way especially if you are intending to do an unattended automation. Just locking the session can hamper the Bot execution because your Runner user should be provided with Auto Login privilege and an active RDP session without any existing session from any other user on that machine.

 

So, I would request to follow any of my approach and let me know if it was helpful or not.

 

Also, kindly check and make sure that you have configured the Screen resolution for the RDP Machine as per standard.

 

 


@Padmakumar according to the Configure auto-login settings page I should be using an existing session for unattended automation with event triggers, and it should be able to unlock from an existing locked session. 

 

 


@Padmakumar according to the Configure auto-login settings page I should be using an existing session for unattended automation with event triggers, and it should be able to unlock from an existing locked session. 

 

 

 

As I have mentioned in my first comment, getting a Black Screen related to the previously active session.

 

Since the given approaches were worked for other fellow members who had faced this issue, I would recommend to give it a try.


Reply