Wait and exit

Wait and Exit are the two flow nodes. Wait pauses a run for a fixed duration; Exit ends it cleanly. Together they shape the timing and completion of every automation.

Wait

A Wait node parks the run for a specified duration. While waiting, the run sits in the waiting state with a wakeAt timestamp visible in the Runs tab. When the timestamp passes, the engine resumes the run on the next scheduler tick.

Fields

• Duration: any value from 1 minute up to 30 days, expressed in seconds.
• Presets: quick-pick chips for 5 minutes, 1 hour, 1 day, 7 days, 30 days.

Common durations

Use shorter waits inside a single session (chat handoffs) and longer waits across days for drip campaigns.

Paused mid-wait

If you pause the workflow while a run is mid-wait, the run keeps its wakeAt. When you resume the workflow, the run wakes either at its original timestamp (if it hasn't passed yet) or immediately on the next tick (if it has). Archiving the workflow cancels all in-flight runs, including waiting ones. See Publish and lifecycle.

Exit

An Exit node ends the run for the current contact. It has no configuration. Once a run reaches Exit, it transitions to completed and is recorded against the workflow's success metrics.

The R9 rule (every leaf needs to terminate)

Every non-Exit node must have at least one outgoing edge. If you leave a node hanging at the end of a branch, Publish refuses with a friendly message:

Send email: Add a next step (or connect to an Exit) so the run knows where to go.

You can wire multiple leaves to the same Exit. There's no limit on how many Exit nodes a workflow has.

Why Exit matters for metrics

Completion metrics (and the green pill in the Runs tab) only fire when a run reaches an Exit. If you skip Exit and rely on the run timing out somewhere, completion stays unrecorded and your conversion stats undercount. Always terminate every branch.

Next steps