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

Change your body as below: 

{

  "deviceIds": {

            "ids" : [152495]

  }

}

 

 

Most Valuable Pathfinder
January 5, 2023

Still, it has same issue

Hi @Shabrez.G 

In Reset Device API please replace below Body and try again

{

  "deviceIds": {

            "ids" : [152495]

  }

}

Note: Make Authentication API call first so token will get refreshed

Chand
Navigator | Tier 3
January 5, 2023

Hi @ChanduMohammad , Now im getting Not found as an error

Navigator | Tier 3
January 5, 2023

In v2 

 

Navigator | Tier 3
January 5, 2023

 

Padmakumar
Premier Pathfinder | Tier 7
Premier Pathfinder | Tier 7
January 5, 2023

 

 

Hi @Shabrez.G,

Please use the correct syntax. Adjust spacing in the same as shown below and try once again.

 

 

Padmakumar
Navigator | Tier 3
January 5, 2023

@Padmakumar Please, can you read the above messages,we have tried all possible test cases

 

Cadet | Tier 2
January 5, 2023

@Padmakumar Please, can you read the above messages,we have tried all possible test cases

 

 

I can’t see it properly used in any of your screenshots. So, I would recommend you giving one last try by following the exact same syntax. As you can see, it’s a solved thread through the very same approach.

Most Valuable Pathfinder
January 5, 2023

Closing the thread, @Shabrez.G is able to make a api call successfully

Chand
Navigator | Tier 3
January 6, 2023

Yes @ChanduMohammad Thanq for you support