Skip to main content
Solved

Terminated during reconcile

  • November 21, 2025
  • 7 replies
  • 109 views
S
Forum|alt.badge.img+2

Hi, we’re having an issue with the error message “Terminated during reconcile.”

We have an AARI process that triggers a bot. After starting the process, a string is entered, which is used as an input parameter for the first task. There is no problem at this point and everything works fine. However, when it gets to the second task, the bot “freezes” and after a few minutes the message “Terminated during reconcile” appears in Audit log (not in History tab, there is nothing about it).

All other bots are working fine. All other AARI processes are working fine as well. The problem occurs only in this one specific case. When I try to run the bot that causes issues in AARI manually (meaning Run bot now), it works without any problems. When I test the same process in the DEV environment, it also works fine. The packages are set to the latest versions.

Could you please advise what might be causing this issue?

 

 

Best answer by Padmakumar

Hi ​@Soky,

 

Generally this error occurs due to some issue/corruption in the AA-DB file in the folder location C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere. The file size reaches more than 300 KB.
 
Resolution/Workaround:
        1. Uninstall the bot agent.
        2. Rename the Automation Anywhere Folder from the path              C:\Windows\System32\config\systemprofile\AppData\Local
        3. Install the Bot agent again

 

Let me know if this doesn't work.

    7 replies

    Padmakumar
    Premier Pathfinder | Tier 7
    Forum|alt.badge.img+15
    • Padmakumar
    • Premier Pathfinder | Tier 7
    • Answer
    • November 21, 2025

    Hi ​@Soky,

     

    Generally this error occurs due to some issue/corruption in the AA-DB file in the folder location C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere. The file size reaches more than 300 KB.
     
    Resolution/Workaround:
            1. Uninstall the bot agent.
            2. Rename the Automation Anywhere Folder from the path              C:\Windows\System32\config\systemprofile\AppData\Local
            3. Install the Bot agent again

     

    Let me know if this doesn't work.

    Padmakumar
    S
    Forum|alt.badge.img+2
    • Soky
    • Author
    • Cadet | Tier 2
    • November 21, 2025

    Hi ​@Padmakumar, thanks for your response.

     

    Where exactly should I do that? We have several unattended runners, and the issue appears on all of them. It’s not related to just one unattended runner. Moreover, I don’t understand why it works when I run it manually. I even tried creating the entire bot again (with a new name), and the problem is still the same.

    Padmakumar
    Premier Pathfinder | Tier 7
    Forum|alt.badge.img+15
    • Padmakumar
    • Premier Pathfinder | Tier 7
    • November 21, 2025

    Hi ​@Padmakumar, thanks for your response.

     

    Where exactly should I do that? We have several unattended runners, and the issue appears on all of them. It’s not related to just one unattended runner. Moreover, I don’t understand why it works when I run it manually. I even tried creating the entire bot again (with a new name), and the problem is still the same.

    Running it manually means, are you still using the same runner machine for that or a different one? 

    Yes, the suggested steps are to be performed on the runner device, as this is a bot deployment issue.

    Padmakumar
    S
    Forum|alt.badge.img+2
    • Soky
    • Author
    • Cadet | Tier 2
    • November 21, 2025

    By “running it manually,” I mean that I don’t start the bot through an AARI process, but simply via Run bot now.

    So does that mean I should perform suggested steps on all machines? We have 7 bot runners, and the same issue occurs on all of them. At the same time, the bot runs fine on all of them when started via Run bot now. It doesn’t seems like this is the solution.

    Padmakumar
    Premier Pathfinder | Tier 7
    Forum|alt.badge.img+15
    • Padmakumar
    • Premier Pathfinder | Tier 7
    • November 21, 2025

    By “running it manually,” I mean that I don’t start the bot through an AARI process, but simply via Run bot now.

    So does that mean I should perform suggested steps on all machines? We have 7 bot runners, and the same issue occurs on all of them. At the same time, the bot runs fine on all of them when started via Run bot now. It doesn’t seems like this is the solution.

    Ok. Access the below article from AA regarding this issue before concluding on this.

    A360 | Bot deployment failing with error "Terminated during reconcile"

    There is always an option to raise a support ticket on this if the provided resolution is not feasible for you.

    Padmakumar
    S
    Forum|alt.badge.img+2
    • Soky
    • Author
    • Cadet | Tier 2
    • November 24, 2025

    Didn’t believe it, but it helped. Thanks.

    Padmakumar
    Premier Pathfinder | Tier 7
    Forum|alt.badge.img+15
    • Padmakumar
    • Premier Pathfinder | Tier 7
    • November 25, 2025

    Didn’t believe it, but it helped. Thanks.

    The pleasure is mine.

    Padmakumar
    Terms & ConditionsCookie settingsAccessibility statement