Browser error is occuring when the bot is running in an unattended mode

I have scheduled an automation in windows schedular. The task is executed successfully with Attended mode, but the browser action is getting error while the machine is in unattended mode or the machine is disconnected. The browser keeps open and no action is executed further and in output the error shown as “Pending Chrome addon to connect”. Would you please give a solution for this.

yes, you cannot do RPA without an active desktop session.
So either ensure your task schedule is set to only run when a user is logged on, and has permission to interact with desktop, or use HD robots

Hey Allan Thanks for being so active in this community. I just signed up to the forum to respond to this.

This use case is working fine for me. So I don’t know what I’m doing right (or wrong :slight_smile: )

I am running a minipc with windows, and I connect via RDP. I just close the RDP window when I want to disconnect.

Here is my workflow

  1. Open Application (Chrome)
  2. Open URL
  3. Login
  4. click some buttons
  5. download some files
  6. do excel to csv
  7. delete excel
  8. close chrome tabs.

Again this is working fine without HD robots, and I am not connected to RDP. I am scheduling via task scheduler!

Let me know how I can share my workflow with you if needed!

You cannot do that.
If you minimize the RDP client, Windows will disconnect the mouse and keyboard from the session. If you disconnect, it will also disconnect the screen.
To keep a session alive using RDP, you need to use HD robots.

Ok, I misread that… Let me clarify.
When you connect to a Windows laptop using RDP, you either log out the user that was signed in at the console, or you “lock” the screen for the console.
While you are connected using RDP, the above rules still apply.
Once you disconnect, the console is STILL locked, meaning there is STILL no keyboard, mouse, or screen.

So either you keep the console running and NEVER connect using RDP… OR you need to use HD robots.

Well for some reason my workflow completes successfully and I get the output files successfully. The browser automation is working perfectly fine. The only trick I did was to use “open application “ before “open URL”. Without this chrome doesn’t open and is in pending state.

@tinker_tut I followed the same process with adding an “Open Application” before Open URL. But unfortunately it is not worked for me. The browser remains open and bot stops executing after that step. Could you please confirm me whether you are using browser automation in your VM (Virtual Machine) and it is in unattended mode. (Either disconnected or signout from the RDP)

I did this video which has the OpenRPA part inside it.

Anyway this is my setup which works fine!

  • Mini PC + Windows 11 (not a VM)
  • I just close the RDP window
  • I changed one parameter which I believe prevents the session logoff (https://youtu.be/eDuGWGiawfQ?t=65) change the parameter to 599940 seconds.