Docs

The Wait node pauses a subscriber journey until a duration elapses or a clock time is reached. Timing starts when the workflow reaches this node, not when the workflow started.

What the Wait node does

The editor offers two types: Duration and At time. Duration waits a set amount of time, then continues. At time waits until a clock time, then continues.

Wait node on the workflow canvas in PushFire

Types of Wait

Duration

Wait a set amount of time, then continue. Starts when this step is reached, not when the workflow started. Example: pause 2 hours.

Units (minimum value is 1):

  • Minutes — short pauses in the same session or day.
  • Hours — same-day reminders.
  • Days — onboarding and re-engagement spacing.
  • Weeks — longer gaps without chaining many day waits.

Duration ignores timezone. It is elapsed time from when the step is reached.

At time

Wait until a clock time, then continue. From when this step is reached, not when the workflow started. Example: the next 9:00, or next Monday at 9:00.

Wait until:

  • Next time — the next time this exact hour and minute happen after this step is reached. If that time already passed today, it waits until tomorrow.
  • Next weekday — the next matching weekday after this step is reached, at the time you pick.

Pick the clock in 24-hour HH:mm. The preview shows the project IANA timezone. Saved nodes that used Next day or In n weeks still preview; pick Next time or Next weekday to replace them.

Timezone

At time waits resolve one date and time in a timezone. Order:

  1. Subscriber timezone — IANA zone on the subscriber, set from the SDK or API. Shown read-only on Audience → Subscribers (Not set when empty).
  2. Project timezone — IANA zone on the project. Used when the subscriber has none.

Set the project timezone when you create a project, or later in Settings → General. At time waits need a project timezone to compute the target date and time. Without it, the editor blocks At time, the canvas marks the node as an error, and the workflow editor asks you to set the timezone before continuing.

Configuring the node

  • Label (required) — why this wait exists, for example Wait until 09:00 next weekday.
  • Type (required) — Duration or At time.
  • Description (optional) — extra context for whoever maintains the workflow.
Wait node editor fields in PushFire

Common use cases

Onboarding

Send a welcome message, Duration wait 1 day, then a reminder. Space later steps with days or weeks.

Local morning send

Use At time → Next time at 09:00 so the next message hits the subscriber's morning when they have a timezone, or the project timezone when they do not.

Weekly checkpoint

Use At time → Next weekday (for example Monday at 09:00) for a weekly digest or check-in.

Troubleshooting

If a Duration wait never continues, check value and unit. Both are required; the minimum is 1.

If At time is disabled or the node shows an error, the project has no timezone. Set it in Settings → General, then reopen the node.

If an At time send lands at an unexpected local hour, check whether the subscriber has a timezone. When it is set, that zone wins over the project timezone.

Legacy Tag waits

Saved Wait nodes of type Tag still run and still show on the canvas (wait until tag conditions match). The editor no longer offers that type. Use a Condition node to branch on tags.

Related guides