Bot Repeatedly Clicking Same Button After Action

Hi ​@Vinothkumar.N,

This does sound like a Recorder‑package quirk that shows up after your upgrade (3.2 → 3.5) and only under certain timing/UI states—so the click finishes, but the step doesn’t detect the post‑click state and replays the same click while still inside the same If branch. In some versions, a Click may default to “wait for object to exist (still)” instead of “wait for object to disappear/state change,” causing the step to believe the action didn’t complete and to re‑issue the click. Intermittency typically depends on page/app responsiveness. 

The locator matches the same button again after the UI refreshes (e.g., SPA frameworks), so the Recorder thinks it still needs to click. AA recommends capturing stable attributes or switching strategy (object vs. window conditions). Some members have confirmed that similar kinds of behavior are resolved by checking Window exists instead of Object exists after the click. 3.5.0 (Dec 2024) was a step before major 4.x/5.x Recorder updates. If your Control Room/Bot Agent allows, upgrading to a later Recorder version often brings Recorder‑runtime fixes. 

In the meantime, you may try the below workarounds:

1) Make the click “transactional” with an explicit post‑condition

• Before the click: add an explicit Wait for object/window to be ready (Recorder → “Object exists” with a short timeout).
• Perform the click (Recorder → Click).
• After the click: wait for a different state that proves success. Options:

             1. Wait until the clicked object no longer exists (Object does not exist) or is disabled.
             2. Wait for the next screen/window (Window exists with the expected title/URL change).
             3. Wait for a new object uniquely present only after the click
             4. Using window conditions is often more stable than object conditions for page navigations. 

Put the post‑condition in a Retry/Timeout loop (e.g., Loop While NOT condition, up to 10–15 seconds with 250–500 ms delay) rather than relying on the Recorder step’s implicit wait.

2) Turn off “smart replay” effect: simulate vs. native events
Re‑capture the button and, in the action’s Advanced properties:

• Switch between Simulate (DOM event) and Send physical events (OS‑level).
• If you used image/coordinates, switch to object (or vice versa) to test. These toggles change how AA decides that a click took place.

3) Stabilize the locator

• Re‑capture and remove volatile attributes (e.g., dynamic IDs, data-reactid).
• Prefer role/aria-label/text and stable CSS/XPath.
• If it’s a web app, capture from a fully loaded state (not mid‑render). If the locator matches a “ghost” duplicate during refresh, AA may reclick it.

4) Guard the IF block

• Set a Boolean flag clickedOnce = False before the IF.
• After a successful post‑condition, set clickedOnce = True.
• Add a short delay of 300–700 ms after the click to allow the UI to settle.
• At the top of the IF block add If clickedOnce = True → Skip. This prevents a double execution if the Recorder step internally retries.

5) Use Wait package instead of Recorder’s implicit waits

Insert Wait for Window/Object actions with explicit timeouts and conditions. These are often more predictable than the implicit wait embedded in the Recorder click

Hello, ​@Padmakumar  Thanks for your Advice and help,

The recorder package upgrade (from 3.2 to 3.5) was done only to resolve the click-action issue. The bot clicks the button or link correctly, but it still tries to capture the same element again. Sometimes it proceeds to the next action,

but if the click happens inside a loop and try catch, the bot repeatedly re-captures the same element multiple times and moving to the next step.so it causes problem

I understood that part. Kindly go through my previous comment and see if any of the suggestions are helping you or not.

As I have already mentioned, you are using an older version of the Recorder package. If your CR allows, please try upgrading the same after checking the Bot agent compatibility. 

Recorder package updates

​@Padmakumar , The issue still remains the same. Even after upgrading the recorder package to 5.0, the problem continues. For the first record, the click works correctly, but after that the bot repeatedly clicks the same button again and fails (action is performed)

​@Padmakumar , tried with default package 5.1 also, it keeps repeatedly clicks the same button again

Ok, apart from upgrading, what else have you tried from my first comment? Also, if possible, share the portal link on which you are trying the Click action to replicate from my end once.

Yes, set delay before capture the button, and also set wait condition check object exist, everything works but keeps repeatedly clicks the same button for initial run it will work later move to other records it fails and this is not new bot which I’m working it is existing bot usually change or update recorder package it works, now facing this issue

Is this happening for all your bots wherever capture action has been used or only in a particular bot? Additionally, are you using the Left Click or Click action?

Kindly share the portal link to test if possible.

[only in pop-up window,

drop-down list,

close pop-up window,

control type is link ]

major for these type, I’m getting this issue

yes, i tried with left click it misses out

cannot share portal, sorry

Have you tried changing the Object Capture technology?

 

Also, you haven't confirmed yet the below:

• Is this happening in all Bots or only in a particular one?
• Are you using the Left Click or Click action?

Hi,

We had a very similar problem roughly two weeks ago. The recorder: capture action ended up looping in refresh the page/fail to select in a dropdown menu. The error appeared randomly, with one bot running successfully, the same bot running 5 minutes afterwards failing.

We ended up switching to another VM as bot runner and got no error at all.

We have contacted the support and are still waiting for the investigation on their side.

P.S. : we did not update any component and it is an on-prem control room, though

EDIT : if you open the  Windows Event Viewer, do you have these repeated errors : VSS (Volume Shadow Copy Service) and COM+ service failures ?

If so, a way to solve the problem would be

• to restart both those services,
• run a  sfc /scannow (cmd as administrato) to repair your Windows OS
• double check if Windows Update or the anvirius does not cause a problem
• You can also try to reinstall the bot agent.

​@Augustin ,

EDIT: if you open the  Windows Event Viewer, do you have these repeated errors : VSS (Volume Shadow Copy Service) and COM+ service failures ?

where I can check this, I found Event viewer, but I have no idea exactly under which tab i need to check

Check under Windows Logs → Application section.

Hi,

We are using the cloud control room. We had this issue about 10 days ago after Chrome got updated to a newer version from 142.0.7444.163. Recorder and browser package updates did not help so we immediately rolled back to 142.0.7444.163 and paused the updates. The issue got resolved. However, yesterday 1 bot machine out of the 4 we have is having difficulty seeing elements on the screen. It keeps on throwing “unable to find link error”. We have reinstalled chrome 142.0.7444.163, bot agent, updated packages to latest and reset global cache. With the latest recorder package, it works intermittently. If we update the browser the repeated clicks problem comes back so we are sticking to 142.0.7444.163. The windows event viewer does not show any errors pointed out by ​@Augustin. Now I am wondering if this could be because of windows update, corruption of files or Crowd strike sensor on the said AWS workspace. Can anyone comment if there is anything new you have found?

Hi ​@Padmakumar ​@Augustin 

It was identified that the VM was configured with only 1 CPU core and 2 logical processors, which caused intermittent click issues.

Now, CPU core count was increased to 4 cores, and the issue has now been resolved.

Regards,

Vinoth