Skip to content

Wait

Pause the workflow for a specified amount of time

Pauses workflow execution for a specified duration before continuing.

Use this node to add delays between actions, implement rate limiting, or wait for external processes to complete.

SettingNotes
AmountHow long to wait.
UnitMilliseconds, seconds, minutes, or hours.

Wait picks how it pauses based on how long it is:

  • Under 1 minute — an in-memory timer. Precise to the millisecond, but tied to the open tab: closing the tab cancels it. That’s fine for the brief pauses this covers.
  • 1 minute or more (in the browser extension) — a durable wait. The run is checkpointed and a browser alarm resumes it at the deadline, so it survives closing the tab, the extension’s background worker unloading, and even a browser restart. Durable waits resolve to within about a minute (the alarm’s granularity) and can run for up to 30 days.

In web/local mode (no extension background), every wait uses the in-memory timer, so a long wait there does not survive a closed tab.

When a durable wait is pending, the run shows as waiting in the Executions pane until its deadline — the same place a Wait For Approval run waits.

When the wait finishes, the data that flowed into the node passes straight through, unchanged, to the next node.

  • No explicit credential or node dependency is declared in the node description.

Place Wait between data-producing nodes and downstream actions to control which data continues through the workflow.

  • Check that required settings are present before running the node.
  • If the node uses browser page data, run it on the target tab after the page has loaded.
  • If it calls an external service, verify credentials, permissions, and rate limits.
  • This node has source tests; use them as the reference for edge-case behavior during maintenance.
  • Filter
  • Merge
  • Wait For Approval — Wait delays for a fixed duration; Wait For Approval suspends the run until a person approves or rejects it.