Skip to main content
Solved

User is already running a bot on device (A360)

  • August 21, 2024
  • 2 replies
  • 256 views

Forum|alt.badge.img

I attempted to run a bot, but it remained inactive for an extended period, so I decided to click on Cancel.

After that, I tried running it again, but I received the following message:

User: (user_id) is already running a bot on device: (device_id)

I also tried deleting the device, but encountered this message:

Cannot delete device, as it is part of an active bot deployment.

To resolve the issue, I have attempted the following actions without success:

  1. Restarted the "Automation Anywhere Bot Agent" service.
  2. Tried to reset the "Automation Anywhere Bot Agent" service, but the service did not appear.
  3. Uninstalled and reinstalled the agent.
  4. Uninstalled the agent and cleaned the AA folders in the user profile.
  5. Restarted the computer.
  6. Left the computer shut down (clean shutdown with no sleep or hibernation) overnight.

Despite these efforts, the issue remains unresolved.

Thank you for your assistance.

Best regards.

Best answer by sano53

Hi ,

This issue happen when you try to RUN and STOP the bot at same time. Because when bot is “Notifying the device” stage you stop the bot you will have this issue.

Resolution:
If you are using Enterprise version of Automation anywhere then you have to call Reset Device API of control room. You will find your device ID in MANAGE>Device then open that device, in URL after myDevice/{deviceid} you will find the device ID.
Then you have to use the Control room Reset Device API with this number.
 

View original
Did this topic help answer your question?

2 replies

Harun 4216
Forum|alt.badge.img
  • Cadet | Tier 2
  • 1 reply
  • August 23, 2024

 Hi please find below doc I hope it will be helpful.

2.try to delete app/data/local and try to rerun.

https://apeople.automationanywhere.com/s/article/BOT-struck-in-In-Progress-Stage-and-not-able-to-move-it-to-history-or-BOT-struck-in-Pending-execution-Stage-and-not-able-to-move-it-to-history-on-A2019-CLOUD-environments/?


Forum|alt.badge.img+1
  • Cadet | Tier 2
  • 2 replies
  • Answer
  • August 25, 2024

Hi ,

This issue happen when you try to RUN and STOP the bot at same time. Because when bot is “Notifying the device” stage you stop the bot you will have this issue.

Resolution:
If you are using Enterprise version of Automation anywhere then you have to call Reset Device API of control room. You will find your device ID in MANAGE>Device then open that device, in URL after myDevice/{deviceid} you will find the device ID.
Then you have to use the Control room Reset Device API with this number.
 


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