Skip to main content
Ground Control | Tier 1
September 22, 2022
Question

Why am I getting this error while trying to run a bot? UNKNOWN: User: (username) is already running a bot on device: If the problem persists, please contact your system administrator.

  • September 22, 2022
  • 28 replies
  • 1204 views

Screenshot 2022-09-22 How to fix this issue?

28 replies

SakthiVel
Navigator | Tier 3
Navigator | Tier 3
September 22, 2022

is there any bot is running already on the device ?

if its shows any activity in in progress , cancel it or move it history and run it again

Lets Connect - https://www.linkedin.com/in/sakthivel-palanisamy-08152833/
Cadet | Tier 2
September 22, 2022

most likely someone has logged in to the Control Room with "X" user from device "Y" and ran a bot.

 

The bot which has been run with "X" user is still running but while it was running on device "Y", you logged in to the Control Room with user "X" from device "T". As soon as you had signed in with user "X" , other session of user "X" in device "Y" dropped. However, your sign in does not effect the bot(stop) running in Device "Y" with the touch of user "X".

 

To me for that reason, you need to first stop that bot running in device "Y" and then retry running the bot through the device you faced with such an error.

 

I hope this explanation will help you.

Navigator | Tier 3
September 23, 2022

Any resolution to this issue? I am now having this same problem.

 

Thank you!

Navigator | Tier 3
September 23, 2022

Same is happening here. The control room was unavailable yesterday around 3PM EST and since it appears that a bot is still running. Even if I shut down the AA bot service, the control room still shows it as connected. I believe this is a host side issue that cannot be solved from the user side. Trying to delete the host gives an error that a bot deployment is in process. Looks like we'll just need to wait it out until AA fixes it.

Navigator | Tier 3
September 25, 2022

I have the same issue on two different accounts on two different machines. As soon as I try to start a bot I get the same message.

Navigator | Tier 3
September 26, 2022

Hey @Sandeep K​  @Robert McDermott​  @Ross Veitch​  @Fred Amiri​  please open the "Task Manager" and end all the "Automation.BotAgent*" task that are running under the "Background Process" tab.

Navigator | Tier 3
September 26, 2022

Hi

This makes no difference. There must be an issue at the backend.

I have gone so far as to completely uninstall the bot agent and then reboot. Exactly the same problem still remains. In task manager I can no longer even see the AA bot agent. But when I log into AA it shows me as still being connected.

When I try to disconnect the device, it refuses to do so because it tells me that there is a bot running.

Navigator | Tier 3
September 26, 2022

imageEnd all these "Automation.ObjectAccessibility..." task using Task Manager. This will solve the issue.

Navigator | Tier 3
September 26, 2022

Apologies - should have posted in the reply but dumped my reply in the main thread.

Navigator | Tier 3
September 26, 2022

Thanks for the help. I don't seem to have those running. But I'm still getting the same error.

 

image