Skip to main content
Navigator | Tier 3
December 29, 2022
Solved

Bots Struck under "In-Progress"

  • December 29, 2022
  • 40 replies
  • 4331 views

Hi Team,

 
I'm currently using the A360 community edition version.
 
I'm facing the below issue and I have tried my best to resolve it but couldn't. It would be great if you could help me resolve this issue as I have done a lot of work on my login and I'm finding it hard to execute the bots now. 
 
Issue Details:
  • I triggered a bot on 21st December 2022 which executed the code and gave the results that were expected, but the bot struck under "In-Progress" with the status "Pending Execution". Till today, the status remains the same and I couldn't execute that bot again. 
           My Action: I have created a new bot, copied the code from the old bot to the new one, and executed it. The new bot worked fine.
  • I triggered another bot on 28th December 2022 (i.e, yesterday) which executed the code and gave the results that were expected, but the bot struck under "In-Progress" with the status "Active". Till today, the status remains the same and I couldn't execute that bot again. 
           My Action: 
                             * Restarted the Automation Anywhere Bot Agent Services - Didn't help.
                             * Reconnected the local device - Didn't help.
                             * Re-Installed the Bot Agent and ran into this error while connecting to the device "System allows only a single device to be registered. If you need to replace your existing device you should delete it first."        
 
I really need this to get resolved to proceed with the POCs that I am doing right now. It would be great if you can help with this as soon as possible. 
 
Screenshots:

 

 

 
Thanks & Regards
Ankith
Best answer by jasthi bhaskar

Hello ​@Ankith K  and Everyone,

The AA team has provided a simplified solution below, replacing the Postman API for resetting the device. checkout this link


Reset device

40 replies

Navigator | Tier 3
January 5, 2023

Hi @Ankith K @ChanduMohammad ,  Can you please help me out with this. As I did all environment changes and kept the device also . but still getting the below error. Can you tell the detail process to overcome the issue

 

 

Most Valuable Pathfinder
January 5, 2023

Hi @Shabrez.G ,

  1. Generate authentication token first, checkout below tutorial,
  1. In the reset device api call delete , in the body line number 3 and Click on Headers section, add X-Authorization and token as shown in the below screenshot for resolution.

 

Chand
Navigator | Tier 3
January 5, 2023

Hi @ChanduMohammad , As you said i added the header and re checked it

Getting a new error, saying reset type is not set

 

Most Valuable Pathfinder
January 5, 2023

Can you click send on Authorization API, token will get refreshed and then try reset api

Chand
Navigator | Tier 3
January 5, 2023

Nope @ChanduMohammad , Still it is getting same issue

Navigator | Tier 3
January 5, 2023

If I run twice or thrice, I’m getting the new issue

 

Most Valuable Pathfinder
January 5, 2023

Remove the curly braises in the Device id body and send the request ex: “ids” : 1234

Chand
Navigator | Tier 3
January 5, 2023

Still the same @ChanduMohammad , Sorry for distrubing you. I donno alot About API

 

 

Most Valuable Pathfinder
January 5, 2023

Still the same @ChanduMohammad , Sorry for distrubing you. I donno alot About API

 

 

No worries, can you click send button of Authorization api and then try resetting device api

Chand
Navigator | Tier 3
January 5, 2023

Still, it has same issue