Skip to main content
Solved

Scheduled Bots Stuck in Queued State

  • February 1, 2026
  • 3 replies
  • 29 views
J
Navigator | Tier 3
Forum|alt.badge.img+5

I have an issue with my scheduled bots where since 7am this morning they have all been stuck in a queued state, with a message that they are waiting for the user and/or device.

I have checked and the virtual machine device is currently connected and the schedule is set up to use the correct user and device.

These bots ran fine for the past few days, but just stopped connecting at 7am this morning.

I can connect to the virtual machine myself, and run the same bot as attended, so the control room is definitely able to connect to the device and there are no issues with the bot itself.

Could this be some kind of firewall issue that would only effect unattended bots? And if so, what can be done to check and resolve this issue?

Best answer by jane.neasham

Thanks for your reply Aaron. 
 

I checked the device listing in the control room and there was only one account associated with the device. I tried removing the device from the account in the User listing and adding it back. That didn’t seem to work at first, but about 15 minutes later the connection restored and the scheduled bots began to run again.

I couldn’t say for definite that what I had done had fixed the process, but they are now working as expected.

    3 replies

    Aaron.Gleason
    Automation Anywhere Team
    Forum|alt.badge.img+14
    • Aaron.Gleason
    • Automation Anywhere Team
    • February 1, 2026

    ​@jane.neasham Check the device listing in the control room. If, for some reason, two or more accounts are associated with that device, it will not run scheduled bots. If that's the case, delete the device entry, log into the bot runner machine, and reconnect the bot agent. 

    If not, let us know and we will come up with something else to try. 

    J
    Navigator | Tier 3
    Forum|alt.badge.img+5
    • jane.neasham
    • Author
    • Navigator | Tier 3
    • Answer
    • February 2, 2026

    Thanks for your reply Aaron. 
     

    I checked the device listing in the control room and there was only one account associated with the device. I tried removing the device from the account in the User listing and adding it back. That didn’t seem to work at first, but about 15 minutes later the connection restored and the scheduled bots began to run again.

    I couldn’t say for definite that what I had done had fixed the process, but they are now working as expected.

      Aaron.Gleason
      Automation Anywhere Team
      Forum|alt.badge.img+14
      • Aaron.Gleason
      • Automation Anywhere Team
      • February 2, 2026

      ​@jane.neasham That is odd, but possibly the secure connection file for connecting the Bot Agent with the Control Room got deleted or became corrupted. Deleting the Device entry was exactly the right thing to do. The new connection will also write a new secure connection file, so you should be working again!

        Terms & ConditionsCookie settingsAccessibility statement