Wait

Step · Stable

Pause execution for a duration, until a timestamp, or until an event fires.

Single-condition wait: set exactly one of duration, until, at_time, or event. duration accepts strings like “2h”, “1d”, “30m”. until accepts an ISO timestamp or a Jinja2 template that resolves to one. at_time accepts a daily wall-clock time “HH:MM” (e.g. 09:00) and resumes at its next occurrence in the workspace timezone — always in the future. event waits for a named platform event with optional timeout. The run enters WAITING state; the scheduler wakes elapsed waits every 60s.

Multi-condition wait (synchronization): add a conditions list with policy: all (wait for every condition) or any (proceed on the first one). This parks the run on a list of conditions — event, signal, or timer — and is about synchronization of WAITING, not parallel compute. A mandatory timeout prevents an all-policy wait from hanging forever. NOT the same as parallel execution (Routario does not support parallel compute).

When to use

Use to introduce a deliberate delay between steps — send a follow-up email 3 days after an initial one, resume at 9am next business day, or hold until a named platform event fires. The run enters WAITING state and resumes automatically; no polling or external scheduler needed.

When not to use

If you need to pause on MULTIPLE conditions simultaneously (e.g. both a timer AND a signal), use Checkpoint instead — it handles the multi-condition synchronization case. If you need a human to provide input before continuing, use Ask Actor.

Inputs

duration

string · optional

Set ONE of duration / until / at_time / event. e.g. 3d, 2h30m, 45s.

until

string · optional

at_time

string · optional

Next occurrence of a daily time, e.g. 09:00 (workspace timezone).

event

string · optional

timeout

string · optional

e.g. 24h.

---

Auto-generated from the skill registry (load_skills()). Do not edit by hand.