Skip to main content
Solved

screen record not work for login page

  • August 7, 2026
  • 2 replies
  • 53 views
D

I have a website where I need to click two links.

First, I click “Click here to login,” which works fine. On the next page, I click “Commvault user,” but that second click always gives me the error below, no matter what I try.

 
“here was a problem at line 3

This may be due to the following reason: Unable to find LINK. Search Criteria did not match. Location: Gui_test (line 3)

To continue, edit the bot and fix the error. Then, try again.

”

 

 

Best answer by Aaron.Gleason

​@DanC25 Sometimes those pages randomize properties for caching or security reasons. When this randomization occurs, it can break the Recorder: Capture actions like you see. 

The fix is to find out which properties change from one login page to the next. After capturing the field in Recorder: Capture, expand out the object properties and take a manual screen shot. 

Then, refresh the page (this might even require closing the browser and/or clearing the cache) and recapture the same object, manually taking another screen shot. 

Now, compare the two screen shots. Which properties changed? Can the Recorder: Capture work if we deselect (turn off) that property? Test all the options. You might even use a wildcard in the field. 

You can also view our video on making resilient automations. It might give you some ideas to make things work. 

    2 replies

    Aaron.Gleason
    Automation Anywhere Team
    Forum|alt.badge.img+6
    • Aaron.Gleason
    • Automation Anywhere Team
    • Answer
    • August 7, 2026

    ​@DanC25 Sometimes those pages randomize properties for caching or security reasons. When this randomization occurs, it can break the Recorder: Capture actions like you see. 

    The fix is to find out which properties change from one login page to the next. After capturing the field in Recorder: Capture, expand out the object properties and take a manual screen shot. 

    Then, refresh the page (this might even require closing the browser and/or clearing the cache) and recapture the same object, manually taking another screen shot. 

    Now, compare the two screen shots. Which properties changed? Can the Recorder: Capture work if we deselect (turn off) that property? Test all the options. You might even use a wildcard in the field. 

    You can also view our video on making resilient automations. It might give you some ideas to make things work. 

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

      ​@DanC25 Excellent sleuthing!

      As for the 6 fields, a trick that you can sometimes do is to use a Recorder: Capture with a Set Test to the first field, set the "delay between keystrokes" to a value like 50 (milliseconds), then pass the first value followed by a tab (in the System values), the next value followed by a tab, etc. By setting the delay >0, it sends the data as keystrokes instead of trying to fill the value into the field all at once. 

        Terms & ConditionsAccessibility statement