Skip to content
Optima docs
ConsoleCampaignsJourneys

Wait node

Hold each profile in a journey for a fixed time, until their best send time, or for a time read from their data.

A wait node pauses a profile before the next step. Use it to give a customer a day to act before a reminder, to send a message at the hour they usually read mail, or to wait for a number of days that is stored on their profile. Add it with Wait in the Add node palette of the journey editor and select Configure.

Who uses it

Campaign creators. Changing the node needs campaign_editor, or another role your administrator has given access to this area — see Licences and roles.

Fields

Wait for chooses the kind of wait. Its fields change with the choice.

FieldMeaningValid valuesDefault
Wait forHow the length of the wait is decided.Fixed duration, Best send time, From the profileFixed duration

Fixed duration

FieldMeaningValid valuesDefault
DurationHow long to wait, as a number and a unit.A whole number of 1 or more, with minutes, hours, days or weeks1 day

In the saved journey the duration is written like 30m, 4h, 2d or 1d12h. If a duration was written in a form the number picker cannot show exactly, the field becomes a text box. Edit it there, or clear it to switch back.

Best send time

Delays the run to the profile's best send hour, read from its best_send_hour signal. This needs the signal to be configured and computed; see Signals.

FieldMeaningValid valuesDefault
Max waitThe longest the run may be held for the best hour.A number and a unit24 hours

From the profile

Waits for as long as a value read at run time says. The value can be a signal, a profile attribute or an attribute of the event that started the run.

FieldMeaningValid valuesDefault
Value to waitThe personalization value to read, for example {{.Profile.Signals.days_to_renewal}}. It must come out as a number. The unit beside it says what the number counts.A personalization value and minutes, hours, days or weeksNone (required)
Max wait (optional)Caps the computed wait. Left empty, the value is still capped at 365 days, so a wrong number cannot park a run indefinitely.A number and a unitEmpty
If the value is missing (optional)How long to wait when the value cannot be read or is not a number. With no fallback, the run continues immediately.A number and a unitEmpty

Actions

  • Choose a Wait for option to switch. Switching resets the other fields.
  • Save in the dialog puts the change on the canvas. Save the journey to keep it.
  • A wait node has one outgoing edge, to the next step.

Examples

Give them two days. Fixed duration 2 days, then a condition that checks whether the basket is still abandoned.

Send the newsletter when they read it. Best send time with Max wait 24 hours, then a send.

Renewal reminder. From the profile, Value to wait {{.Profile.Signals.days_before_reminder}} in days, Max wait 60 days, If the value is missing 3 days.

Common problems

  • The editor says Set a wait duration. A fixed wait needs a number of 1 or more.
  • The editor says Set the value the wait is read from. From the profile needs a Value to wait.
  • Runs do not wait for the best hour. The best_send_hour signal is not configured, or was not computed for that profile.
  • Runs wait much shorter than expected. The value came out missing and there is no fallback, so the run continued at once. Add a fallback.

On this page