Skip to main content
Question

Recorder steps failing across multiple bots


Forum|alt.badge.img+4

I just wanted to see if anyone has suggestions or thoughts I have not tried yet. Beginning late Wednesday, bots in our production space began failing intermittently when trying to log into websites. They were simply failing to see elements on the page, and randomly - a button here, a drop-down there. It started with 2 bots and then escalated to over a dozen.

I confirmed all of these same processes work fine in Dev. They are same code versions, same Chrome versions, same plug-in and Bot Agent versions, and same package versions. I rebooted the production VMs, cleared cache, etc. Logs show me only that the element wasn’t found. I tried recapturing some of the commonly failing Recorder steps, and for some it worked while others still do not.

As of this morning, the processes are now all failing in Dev as well. Same issues, random Recorder steps simply not finding the element. I have created a support ticket, and am waiting on a response, but at this point all of production is spotty. Just looking for thoughts on anything else to try.

7 replies

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+10
  • Automation Anywhere Team
  • 514 replies
  • March 21, 2025

Try this:

Record the DOMXPATH and Path of a few objects that are failing. Then recapture the objects and compare the DOMXPATH and Path. See what changed. It could be the ID or any of the other parameters too, but is typically the DOMXPATH or Path. 

If they have changed, something is different in your environment or the application you're trying to work with. Maybe IT pushed a new version of a browser silently or someone made a change on the site. 


Forum|alt.badge.img+17
  • Flight Specialist | Tier 4
  • 86 replies
  • March 21, 2025

Thanks, ​@Aaron.Gleason, for the suggestion, I am running through this now. I noticed now we are seeing issues with the Recorder capture (below) that we were not experiencing before. This is on all Dev VMs; the capture reticle is off on all elements. I have confirmed resolution/zoom levels are the same, etc. I have gone so far as to uninstall/reinstall the bot agent completely on one, with no change; just so bizarre the flurry of issues.

 

 


Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+10
  • Automation Anywhere Team
  • 514 replies
  • March 21, 2025

It appears you’re trying to connect to *.medsolutions.com. It appears the site is having problems today. I’m getting all kinds of timeouts trying to connect to them.

If you get that weird, floating capture box like above, that’s because it has identified something that is floating there. You can click on that phantom object and look at the properties to see what it is. By the way, good on you for verifying zoom and resolution. 👍


Dineshkumar Muthu
Navigator | Tier 3
Forum|alt.badge.img+9

Hi ​@JLogan2024 

  • Verify whether two Automation Anywhere (AA) plugins are enabled in the browser. If so, remove the older plugin and retain the latest version.

  • Ensure that the screen resolution used during bot development aligns with the resolution of the production (PRD) device.


Forum|alt.badge.img+17
  • Flight Specialist | Tier 4
  • 86 replies
  • March 21, 2025

@Dineshkumar Muthu regarding the plugin thanks, I did confirm there is only one present, the latest 3.4.2.0. As mentioned above, resolution is the same on all devices.


Forum|alt.badge.img+8
  • Navigator | Tier 3
  • 58 replies
  • March 21, 2025

If you want to confirm that environment is not an issue, run the bot in attended mode in both environment and if everything works, code is not the problem.


These issue happen when bot is unable to keep the screen active in unattended mode.


Forum|alt.badge.img+17
  • Flight Specialist | Tier 4
  • 86 replies
  • March 21, 2025

@Bot Dev thanks, as mentioned above, on Day 1 it was failing in Unattended in Production but working find (Attended) in Dev. As of this morning, it is failing in Attended mode in Dev as well.

My plan had been to simply recapture a number of the steps and try that, but with the Recorder issue we’re not experiencing I have been unable to do this yet.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings