Skip to main content
Solved

Recorder: Capture steps are sporadically failing across multiple bots and multiple websites

  • September 30, 2026
  • 4 replies
  • 191 views

We’ve had a few bots running for several months now that use many Recorder: Capture actions to extract info from and input info into certain websites. For months, they’ve been running fine daily or multiple times per day without issue. As of Saturday 9/26, they've been failing.


The cause of the failure is that Recorder: Capture steps are failing. They are failing inconsistently, and I can’t identify any pattern as to why this is occurring. If I rerun the same bot multiple times, it might fail at a different Capture step each time, but the point of failure is always a Capture step. 

 

If the bot fails during its run, I’ll get a “unable to find CLIENT. Search criteria did not match” error. Sometimes, the bot won’t stop at the error - it will just fail to get a property that it was supposed to capture and cause issues downstream (e.g. a variable it was supposed to capture will be empty, so it will think it failed to input a particular value). 

 

This happens whether the bot is being run attended or unattended. I’ve tried making changes to the individual bot steps - such as changing which object properties are used to identify the object to capture, changing the technology type to capture the object to Microsoft UI Automation, recapturing the DOMX path, adding delays before or after the capture steps, and embedding the capture steps within error actions to reattempt in the catch, but these have not resolved the problem. 

 

Because this issue is impacting not just one bot or website, but many, this appears to be an issue that cannot be resolved by fixing individual bots. I’ve tried uninstalling and reinstalling the bot agent and Chrome extension, clearing the Chrome cache, running the bot on a different VM, and running the bots attended instead of unattended, but none of these have fixed the issue. 

 

What else can I try on a system level to try and fix this issue? What are the potential causes of Recorder: Capture steps suddenly beginning to fail sporadically on every website on which the bot uses them?

Best answer by Brady Principe

Hola prueba lo siguiente,

En google chrome ingresa a configuracion y luego a rendimiento, desactiva precarga de paginas.
Luego ir a IA y desactivar. Luego en Sistema desactiva todos menos aceleracion de graficos.

saludos
 

View original

4 replies

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+6
  • Automation Anywhere Team
  • September 30, 2026

​@dylan.clark Someone posted on another thread that they thought the latest Chrome update broke their Recorder: Capture actions. Try rolling back the version of Chrome and try it again. 


Hola prueba lo siguiente,

En google chrome ingresa a configuracion y luego a rendimiento, desactiva precarga de paginas.
Luego ir a IA y desactivar. Luego en Sistema desactiva todos menos aceleracion de graficos.

saludos
 


Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+6
  • Automation Anywhere Team
  • October 1, 2026

From ​@Brady Principe 's post:

Hello, try the following:

In Google Chrome, go to settings and then to performance, then disable page preloading.
Next, go to AI and disable it. Then, under System, disable everything except graphics acceleration.

Regards


  • Author
  • Cadet | Tier 2
  • October 1, 2026

Hola prueba lo siguiente,

En google chrome ingresa a configuracion y luego a rendimiento, desactiva precarga de paginas.
Luego ir a IA y desactivar. Luego en Sistema desactiva todos menos aceleracion de graficos.

saludos
 

Thank you so much - this fixed the problem!

How did you figure this out? Are these settings that were new, or newly set to default, with this latest version of Chrome?