Error: The web page took too long to load. Increase wait time and try again.

Hi ​@MJunaidS123,

as I said before try to use just the DOMXPath and de-select all other ones like this…

 

Hi ​@MJunaidS123 

Possible Causes and Solutions

• Cause1: The web page might be loading dynamically, causing elements to appear after the initial page load. The bot might be trying to interact with the element before it’s fully rendered.
• Solution:
  • Explicit Wait for Element: Instead of a generic wait, use the "Wait: Wait for condition" action with a specific condition:
    • Condition: "Object exists" (select the target element using the Recorder).
    • Set a timeout (e.g., 30-60 seconds) to give the page ample time to load.

• Cause2: The element’s properties (e.g., ID, class, XPath) might be dynamic, causing the bot to fail to locate it consistently, even if it’s visible.
• Solution:
  • Recapture the Element: Use the Recorder to recapture the element and ensure the properties are stable:
    • Prefer static attributes like id or name over dynamic ones like class or index.
    • If no static attributes exist, use a relative XPath or CSS selector (e.g., //div[contains(text(), 'StableText')]).
  • Wildcard Properties: In the Object Properties (Recorder settings), use wildcards (e.g., *) for attributes that change (e.g., id="button_123" → id="button_*").
  • Validate Element: After capturing, use the "Object: Get property" action to test if the bot can find the element and retrieve a property (e.g., innerText). Log the result to confirm

• Cause3: The browser or web application might be running slowly due to system resource constraints, network latency, or heavy scripting on the page.
• Solution:
  • Switch Browser: If using Chrome, try switching to Microsoft Edge or vice versa in the "Browser: Open" action. Ensure the browser extension for Automation Anywhere is installed and enabled.
  • Close Unused Tabs: Add a "Browser: Close all tabs" action before starting to free up resources.
  • Check System Resources: On the bot runner machine:
    • Open Task Manager and ensure CPU/memory usage isn’t maxed out (e.g., >90%).
    • If it is, close unnecessary applications or increase the machine’s resources (RAM/CPU).
  • Network Stability: Test the network connection. If it’s unstable, the page might not load fully. Contact your IT team to rule out network issues.

• Cause4: The "Window: Activate" workaround didn’t work, possibly because the browser window isn’t fully in focus or the UI isn’t rendering correctly for automation.
• Solution:
  • Maximize Window: Use "Window: Maximize" after "Browser: Open" to ensure the window is fully visible.
  • Simulate Keystrokes: Add a "Simulate Keystrokes" action (e.g., press F5 to refresh the page) before interacting with elements to force a reload.
  • Delay After Activation: Insert a small delay (e.g., 2-5 seconds) after "Window: Activate" to allow the UI to stabilize.

​@MJunaidS123  did any of these solutions help you out?

Hi ​@MJunaidS123 ,

If you haven't tried yet, please implement the Loop → While with Object Doesn't exists condition by passing any expected Object in the page.