Skip to main content
Solved

Bot stuck "connecting to device" while in queue

  • October 25, 2024
  • 2 replies
  • 66 views

Forum|alt.badge.img+1

Hi, I didn’t want to spam the same topic again but I didn’t find a solution for my issue anywhere.

I have this community edition CR and I was following the tutorials in the “START” phase, in the last lesson they were teaching about “Learning Instances” which I got to know got changed to “Document Automation”

While deploying to the queue, the bot got stuck in the “connecting to device” status and it hasn’t moved since, there were originally 5 instances in the queue to be processed but I think they timed out and failed, and after 24 hours there’s still one left as you can see in the ss.

I cannot remove the device, nor can I deploy any other bot, until this deployment is resolved/removed.

How can I force stop this deployment? How can I force remove a device from the CR? Why does it keep asking me to check with the “administrator”, I’m the only person using this account for learning purposes, is there a way around that admin privileges issue? Thanks in advance!

 

 

 

Best answer by Aaron.Gleason

Try the page I built:

https://rpademo.automationanywhere.com/deletedevice.php

View original
Did this topic help answer your question?

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+10
  • Automation Anywhere Team
  • October 25, 2024

Forum|alt.badge.img+1
  • Cadet | Tier 2
  • October 25, 2024
Aaron.Gleason wrote:

Thanks Aaron, I don’t know what changed because I tried this solution yesterday and nothing happened, but now it worked flawlessly. FWIW if anyone is seeing this I also uninstalled the automation anywhere bot & “nuked” the automation anywhere folders as mentioned in this thread:

 

https://community.automationanywhere.com/community-edition-85050/as-of-9-30-2024-i-can-no-longer-see-the-windows-service-and-cannot-stop-a-bot-running-88845?postid=97755#post97755

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings