Issue with recorder command after the latest chrome update to version 154

Question

I am facing issue in the production bots relating to recorder package after the chrome updates. It is failing abruptly although there is no change on the web application. Is anybody facing the same issue ? What measures have you taken to ensure the bot run.

KhaledMostafaMe · Accepted Answer

This issue frequently points to a broken Chrome extension rather than the web elements themselves. To isolate the problem, try capturing any random element on a completely different page (like google.com).

If the capture fails everywhere (Extension Issue):
- Check chrome://extensions/ to ensure the Automation 360 extension is enabled and has site access.
- Remove and reinstall the extension.
- Restart the Automation Anywhere Bot Agent service via Windows Services (services.msc).
- Update to the latest Recorder package in your Control Room.
If the capture works on other pages (DOM Issue):
- The extension is functioning, but the Chrome update altered how your specific web application's elements render. You will need to manually recapture the failing elements in your bot to update their properties.

Also, what is the exact Chrome version currently installed on the affected machines?

Aaron.Gleason · Answer

​@Nazreen Bano This is an unfortunate consequence of updating software. Sometimes the authors of the software (Chrome, in this case) make significant changes to the way objects are used and displayed.What I would recommend is to make a copy of one of the troublesome automations, note all the properties of the Recorder: Capture that is failing, recapture the object and then compare the updated properties.If there are no differences, the issue is something else. Maybe the web application did go through an update.If there are differences, the issue is the Chrome update. At that point, you need to consider whether to roll back Chrome to an earlier version to keep your automations running, or to make updates to all the applications using that web app by updating all the Recorder: Capture actions. This process seems daunting, but can usually be knocked out pretty quickly by an experienced automator because usually it only requires recapturing the objects, not re-writing the entire automation.

Sign up

Login to the Pathfinder Community