Wait Until

The Wait Until node pauses a campaign execution until one or more release rules are satisfied.

When to use it

Use this node when a fixed delay is not enough.

Common examples:

• wait until a contact meets profile or segment conditions
• wait until a timestamp from the trigger event
• wait up to a maximum amount of time before continuing
• branch contacts differently when the wait condition is not met

Settings

• Conditions: attribute, event, segment, or message conditions the contact must satisfy.
• Event time: waits until a timestamp from the trigger event payload.
• Max time: the longest a contact can wait before the node releases them.
• Not Met branch: optionally creates a second output path for contacts released without meeting the condition.
• Simulation path: lets simulations choose whether the contact exits through the Met or Not Met path when both are available.

Simulation and execution behavior

Simulations use the node's simulation path setting to decide which output to follow. Real executions hold the contact until a configured release rule applies.

If Max time is disabled, contacts can wait indefinitely until conditions are met. Use that intentionally and review the warning shown in the node editor.

Best practices

• Add Max time unless indefinite waiting is the intended outcome.
• Enable the Not Met branch when the workflow needs a timeout or fallback path.
• Use clear node names when multiple wait nodes appear in one campaign.
• Test both Met and Not Met simulation paths before publishing.

Related guides

• Time Delay
• If / Else
• Publishing and Simulating Campaigns