Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

delay

Pause the run for a duration — durably.

steps:
  - id: submit
    send_transaction: { ... }
  - delay: 30s
  - id: verify
    read: { ... }

The action is just the duration string: 30s, 5m, 2h, 1d.

Durable means durable

delay is not a sleep. The wake-at timestamp is persisted to the journal (waiting_delay state) before the wait starts, so:

  • a restart or crash mid-delay resumes the countdown against the persisted wake time — it neither resets nor skips
  • a delay that elapsed while the process was down fires immediately on recovery
  • long delays (hours, days) are safe and cost nothing while parked

When to use it

  • settling time between a send and a verification read
  • pacing between actions to a rate-limited API
  • fixed "wait then check" patterns — when you are waiting for a specific onchain event rather than a duration, use the wait_for: step instead (it races events against a timeout)