Skip to main content
The Delay node pauses the run before continuing to downstream nodes. Use it for rate limiting, polling intervals, waiting on slow external jobs, or multi-day drip sequences.

​
Configuration

FieldWhat it does
DelayHow long to wait, in the chosen unit (minimum 1)
UnitSeconds, Minutes, Hours, Days, or Weeks
Wait Message (optional)Text shown while the run is waiting

​
How long delays work

  • Up to 15 minutes: the run waits in place and continues as soon as the time is up.
  • Longer than 15 minutes: the run suspends and a wake-up is scheduled. The execution shows a waiting status in Execution logs and resumes automatically at the scheduled time. Suspended delays are durable: a delay of days or weeks survives backend restarts and deploys.
Example: a video generation node kicks off a render, a Delay node waits 2 minutes, then an HTTP request polls for the finished file. Or in an onboarding flow: send a welcome email, Delay 2 Days, then send the follow-up.
Delays pause the whole path, not just one node. Everything downstream of the Delay node waits until it completes.

​
Agent scheduling: the Alarm node

The Delay node pauses a running workflow. If you instead want an AI agent to schedule its own future wake-ups (countdowns, specific times, or recurring cron schedules), wire an Alarm node into the agent. See Agent scheduling.

​
Next steps