Wait Until

Pause a flow until a date/time or a condition is met.

What “Wait Until” does

The Wait Until step pauses a flow so actions happen at the right time.

Typical use cases:

  • Send a reminder 24 hours before an appointment
  • Wait until a specific date (like a follow-up date)
  • Delay internal tasks so they don’t fire immediately
1

Add a Wait Until step

Add a Wait Until step where you want the flow to pause.

2

Choose what you’re waiting for

Pick one: - A specific date/time - A contact field (example: wait until appointment_date) - A condition becoming true - A trigger event (example: tag/list changes, board stage changes, email activity, form/quiz completion)

3

Test with one contact

Trigger the flow with one test contact and confirm it resumes when you expect.

Wait event options (current)

Wait Until supports common flow event types, including:

  • Tag/list added or removed
  • Board stage changed
  • Contact property changed
  • Email opened or clicked from a flow or campaign send
  • Anniversary date and exact date rules
  • Booking before/after start-time offsets
  • Order paid and order status change
  • Form submitted, quiz completion, quiz score, quiz outcome, and quiz answer events

Use the option that is easiest to verify with one test contact first.

Date-based wait setup updates

  • Date waits support built-in and custom date fields.
  • You can configure before / on / after timing rules.
  • You can set an explicit trigger time (hour/minute) for date waits.
  • You can optionally include/exclude specific lists so the wait only applies to matching audiences.

Matching and timeout controls

  • Tag and list waits can require any selected item or all selected items.
  • Board stage waits can target a specific board and stage.
  • Booking waits can target any event type or a selected event type, with before/after offsets.
  • Form, quiz, and survey waits can listen for any item or a specific selected item.
  • Use Enable timeout when a contact should not wait forever if the event never happens.

Best practices

  • Prefer clear, predictable delays (e.g. “wait 1 day”) when possible
  • If the timing is critical, test the flow with a sample Contact
  • If your flow supports timeout controls, set a timeout to prevent contacts from waiting indefinitely.

If a contact doesn’t have the date/field you’re waiting on (or it never updates), the flow can appear “stuck”.

Common examples

Troubleshooting

If a flow appears “stuck”, check:

  • The wait condition and time zone assumptions
  • Whether the flow step is waiting on data that never becomes true
Flows Troubleshooting
Fix common issues like “stuck” contacts and missing triggers.
Updated May 3, 2026

Was this helpful?