Usually the next step in an automation is a Recorder: Capture. These Recorder: Captures are tied to the URL/window title that you’re automating and have a default time-out of 15 seconds. By capturing something on the next expected page, the Recorder: Capture will automatically wait until that object is ready. No need to wait for a page to load in most cases.

Thanks Aaron. The next action is ‘Keystrokes’ to Tab and interact with an export button. Unfortunately I’ve tried using Recorder: Capture but it does not interact well with objects on the page. They are loaded in before the URL changes, just that some properties of the objects change e.g. paragraph text or a button becomes active. The most reliable way of detecting changes on the page is the change in URL. Is there a way I could extract this into a string and loop until there is a change? Or another way using the URL?

I don’t know what the full URL will be at the beginning or end so I will need to capture this.

You can also have a loop and inside check If Object exists (if yes the break the loop and continue with you remaining steps) in else put delay for 1-2 seconds.

Make sure to have a counter in place to exit the loop should the object not be detected to avoid infinite loop issues.