Hi ​@Poornima ravi,

Even if the portal looks fully loaded, AA360 may fail to “see” objects if any of the following changed under the hood:

• Tab/window title text changed (Edge often tweaks the suffix: e.g., " - Microsoft Edge" → " - Work - Microsoft Edge").
• DOM attributes for your label/refresh button changed (IDs/classes get regenerated, elements switch from <label> to <div>/<span>, etc.).
• The target moved inside an iframe or shadow DOM (AA won’t find it unless you switch context).
• The Automation Anywhere Edge extension lost its connection after the Edge update (AA then can’t read the DOM reliably).
• The page is a SPA (React/Angular) — document.readyState = "complete" happens before your controls are actually attached or become visible.

Check the below things first:

1. Edge extension status

   • In AA Bot Agent (system tray) → Extensions → confirm Microsoft Edge shows Connected.
   • In Edge, the Automation Anywhere extension is On, Allow in private (if used), and Site access is allowed for your portal domain.

2. Window/tab title change

   • Manually read the exact tab title in Edge. If it now ends with " - Work - Microsoft Edge" or a profile name, your “Window with same title exists” will fail.
   • Fix: Use partial match or wildcards:
     • Window: If window exists → Match = Contains → PortalName (avoid the Edge suffix altogether).

3. Re-capture and test the objects

   • Recapture the label and Refresh button.
   • In the object definition, avoid volatile attributes (ID with GUIDs, dynamic class hashes). Prefer:
     • aria-label, role, name, stable innerText, data-testid, title, or relative xpath/css with contains().
   • Use Test Object in the Recorder to confirm it matches at runtime.

4. Check for iframes or shadow DOM

   • Right-click → Inspect in Edge → see if target sits under <iframe> or a #shadow-root.
   • If shadow DOM: DOM-based selectors may fail; use Run JavaScript to pierce shadow roots or switch to Computer Vision as a fallback.

Hi

1.edge extension is on

2.i have already given it is *GPMS*

3.I have recaptured the recorder commands and already have disabled the paths

It still doesn’t recognize 

Could you please provide the URL so that I can try from my end once?

Hi 

i won’t be able to give the url.

regarding the 4th point i have attached the image.

does the recorder packages have to be updated?

It seems like there is some issue in viewing your attachment.

 

Unfortunately, I am unable to reach any conclusion from this image. Are you using DOMXPath as the Object property? If so, is it customized? 

Yes , not customized but whatever the recorder has captured is enabled

The image is the inspect the element of the label

For this reason only I had asked for the URL so that I can inspect it and try to create a custom DOMXPath. As you are using the default one, it can fail considering the dynamic behavior of the portal.