I have developed a bot that is working fine on a EC2 virtual machine using a Remote Desktop Session but is failing when I am disconnected or when I minimize RPD-session (and the bot is initiated by Orchestrator). My Unattended Robot has to open browser and click some buttons but it doesn’t work under locked screen / minimized RDP-Session while everything works fine on maximized RPD both from orchestrator and from Assistant.
When the process fails on Orchestrator, I connect to RPD again and I notice that the browser is open but no button is clicked (Timeout reached alert). For this reason I think it could be a GUI problem with disconnected RPD.
Any advice?
This is an expected behavior then. Community Edition of the Studio have some limitations over the unattended config because the Robot Service is deployed in the user mode. Take a look on this documentation:
Thank you for your quick answer @Pablito,
Now I can’t undestand how to switch from User Mode to Windows Service. I read about
“Converting Robot Deployment Type” but I can’t do it from Command Prompt, can you help me with a detailed guide? Is Enterprice Edition necessary to work with Service Mode Robot?
Any advice is useful for me
I am facing the same issue, but I have a enterprise version and using computer vision activities, normally robot could able to open the application but then getting timeout when I am unattended. It works totally fine when I am on screen while process runs. What could be the possible issue?
Please check if your robot is configured as the unattended. Eventually you can open a case for our Technical Support so they will be able to help you directly.
Thank you @Pablito . Currently robot is set to NonProduction, That seems to be the issue right? I only have two licences for Unattended and both are used.
ashokkarale
MD_Farhan1
Ajay_Mishra
postwick
Dheerendra_vishwakarma
Anil_G
chandreshsinh.jadeja
Gautham_Pattabiraman
vrdabberu
aravindbalineni123