Wait Block
Wait pauses the Flow for a configured duration, then continues to the next connected Block.
At a glance
What it does
Wait adds a fixed delay. It is the simplest way to give a page, popup, or external service time before the next Block runs.
Prefer Wait For Element when a reliable selector exists. Fixed delays are easier to configure, but they are less precise.
Use it when
- Pause briefly after an action that triggers animation.
- Give a slow page a fixed delay when no stable selector is available.
- Throttle a Flow between actions.
Do not use it when
- A specific element can tell you the page is ready; use Wait For Element.
- You need retry logic or error handling.
- The delay would need to be longer than 60 seconds.
Settings
Wait has one duration setting. The UI can show the duration in milliseconds or seconds, and the runtime caps the delay at 60000ms.
Duration
Required: No- Variables
- No
- Description
- Delay before continuing. The schema default is 1000ms and the maximum is 60000ms.
Outputs
Wait does not create a reusable variable. The run output can record the delay that was applied.
delayMsnumberDelay in milliseconds applied by the cloud runtime.
Example Flow
Use Wait as a short buffer when the next page state is time-based rather than selector-based.
- Run the action that starts a page transition.
- Wait for a short fixed duration.
- Continue with the next Block.
Errors and fixes
Start with symptoms visible in the editor or Inspector, then check the earliest Block that produced the wrong page state, variable, or output.
The next Block still runs too early.
- Check
- Check whether a stable page selector exists.
- Fix
- Use Wait For Element instead of increasing the delay blindly.
The Flow feels slow.
- Check
- Look for fixed waits that can be replaced by selector waits.
- Fix
- Reduce the duration or switch to Wait For Element.
Local and cloud runs
Local and cloud runtimes both sleep for the configured duration. Cloud clamps the delay to a maximum of 60000ms.