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

​@MJunaidS123 I’m moving this to Community Edition. Could you help us with the following details:

• which training are you following?
• which package are you using?
• what are you trying to build?

This additional context will help us help you.

Hi ​@MJunaidS123,

try to use the DOMXPath only and see what happens.

How to check for the DOMXPath in developer tools see here:

https://youtu.be/uKHJtLHLmVo

Cheers

Marc

Thanks Shreya

• We have just started using the tool so looking at Getting Started with Your First Automation 
• Package being used in Recorder:  4.0.5-20250221-030633
• Package being used in Browser: 3.13.1
• Steps: Navigating to https://rpademo.automationanywhere.com/ and entering a Username and Password, thereafter logging in - using the Recorder: Capture tool

Hi ​@MJunaidS123,

try to use the DOMXPath only.

How to use the developer tool in browser see below 👇 

Let me know if this was helpful please 😊!

Cheers

Marc 

​@MJunaidS123 if you still having problems you might want check your zoom level in browser to be at 100% and/or screen resolution is correct.

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/aae-client/bot-creator/commands/cloud-using-recorder-action.html

Cheers

Marc

Thanks. Have been through the video, used Browser: Run JavaScript but still not working.

Unfortunately, still no luck after using Run JavaScript with specific Id

​@MJunaidS123 have you specified a browser to open?

Screen resolution and zoom level is fine?

Browser extension is active?

What do you see in the Botrunner logs?

(C:\ProgramData\AutomationAnywhere\BotRunner\Logs)

Post a screenshot from your code would also help.

Cheers

Marc

Hi Marc, I don’t seem to be able to find those logs within my folder. It might be best if I could go through this with someone over a call. Is this something supported by the Automation Anywhere team?

​@MJunaidS123 someone from the team may not be able to assist you over a call, but a volunteer community member sure can!

As ​@Marc Mueller mentioned, I would recommend posting screenshots of settings of the recorder action that fails, so we can help understand the context better!

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.