Skip to main content
Answer

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

  • June 22, 2022
  • 1 reply
  • 258 views

Control room shows "cannot delete device, as it is part of an active bot deployment". I should note that the bot agent is already uninstalled on the mentioned device. Since I am unable to connect more than 1 device to the control room, I'm stuck here. Any solution to this?

Best answer by Nishanth Anbalagan

Hi @Darren Tan​ 

 

Usually only one device can be a part of control room, if you signed in on any other device please delete the device from that older machine.

 

Try uninstalling the Automation Anywhere software on that device itself. During the uninstall it will ask do you want to remove this device from control room. mark yes. Reinstall on the device if you need it for AA somewhere else.

 

Please refer the below article:

https://apeople.automationanywhere.com/s/question/0D52t000018kiLOCAY/i-am-unable-to-delete-the-device-as-it-says-it-is-a-part-of-an-active-bot-deployment/p>

 

https://apeople.automationanywhere.com/s/question/0D52t00000KSgsXCAT/cannot-delete-device-as-it-is-part-of-an-active-bot-deployment?language=en_US/p>

 

 

Thanks,

Nishanth

This topic has been closed for replies.

1 reply

Forum|alt.badge.img+4

Hi @Darren Tan​ 

 

Usually only one device can be a part of control room, if you signed in on any other device please delete the device from that older machine.

 

Try uninstalling the Automation Anywhere software on that device itself. During the uninstall it will ask do you want to remove this device from control room. mark yes. Reinstall on the device if you need it for AA somewhere else.

 

Please refer the below article:

https://apeople.automationanywhere.com/s/question/0D52t000018kiLOCAY/i-am-unable-to-delete-the-device-as-it-says-it-is-a-part-of-an-active-bot-deployment/p>

 

https://apeople.automationanywhere.com/s/question/0D52t00000KSgsXCAT/cannot-delete-device-as-it-is-part-of-an-active-bot-deployment?language=en_US/p>

 

 

Thanks,

Nishanth