Process fails to identify web elements when not logged into server

[Abai]

Hello Community,

I am facing an issue with a process I developed on the Blue Prism server. The process runs successfully end-to-end when I execute it from Process Studio or Control Room while I am logged into the server via RDP.

However, once I disconnect from the server (log out/close RDP session), the process fails because it can no longer identify most of the web elements.

It seems like the bot only works when the desktop session is active, but fails to interact with applications when I leave the server.

Has anyone experienced this issue before? How can I configure Blue Prism so that the process can run unattended and still recognize the web elements even when I am not logged into the server?

Thanks in advance for

your help!

[david.l.morris]

When you say "server", are you saying the machine has the Windows Server operating system? I personally have little experience using servers as Runtime Resources. I wouldn't expect the issue you're describing if it truly is a windows server OS, but I dunno for sure. If you're saying server as a generic term and they actually have Windows 10/11 on them, then the reason it fails after closing out of the RDP session is that disconnecting from RDP basically locks the screen of that session, and you can no longer automate the screen after that until you log out and back in or restart the machine. I'm sure it's more complicated than that it's just locking the screen, but this is the way I think about it practically speaking. If you don't have some other way to view the desktop that doesn't use an RDP connection (such as vSphere, Team Viewer, or other), then I'd say you can at least solve your problem by restarting the machine or logging it out after you exit the RDP session. Then let Login Agent log the machine back in, and then your process should work.

[Abai]

Thanks for the response. The screen doesn’t lock after I disconnect from the RDP session, the process still launches the browser and navigates to the login window as expected. The issue is that it’s unable to input the username because it doesn’t recognize or match the element once the RDP session is closed.