3.2 Wait Activities and Timing Modulation

3.2 Wait Activities and Timing

A Wait pauses an individual journey execution. It is useful for cadence, business timing, and giving a customer time to act, but it must be selected according to the actual requirement.

The three wait modes

Duration waits for an elapsed interval, such as two hours or three days after the profile reaches the activity. Use it when relative timing matters.

Custom calculated date releases the profile at a date and time calculated from available data. Use it for a due date, appointment-relative reminder, renewal date, or another profile-specific calendar target. Validate what happens when the source is missing or invalid before publishing.

Send-time optimization uses Adobe's prediction to select a time within the configured window when the person is more likely to engage. It requires the applicable feature and sufficient engagement data. It is not simply “send at 9 a.m. in the profile's time zone.”

Do not invent a separate generic “Wait until date” mode when the current interface describes the calendar option as Custom calculated date.

Limits

A single Wait can be at most 90 days. A person's entire journey is subject to the 91-day timeout. Multiple waits, channel processing, and other activities all consume that lifetime. Two waits of 60 days do not create a valid 120-day execution; the journey timeout still applies.

When a use case spans many months, design bounded journeys connected by durable data or supported entry patterns. Keeping a profile parked on a canvas is not long-term state management.

Time zones

The journey's time zone is configured in journey properties and affects scheduled interpretation. Journey Optimizer can also use the profile's time-zone preference, sourced from the standard Preference Details field, with a configured fixed time zone as fallback when appropriate.

A phrase such as “send at 9 a.m. local time” is incomplete until you know:

• whether the required profile time-zone field is populated;
• what fallback applies;
• how daylight-saving transitions are handled;
• whether the target uses journey time or profile time;
• whether the calculated date includes an offset.

Test profiles from several time zones and one missing-zone profile. A global audience tested only in the author's local zone can appear correct while being wrong for most recipients.

Wait versus reaction

A fixed wait says, “pause, then continue.” It does not listen for an event during the pause. If the requirement is “continue immediately when a purchase arrives, but take another path after 48 hours,” use a supported Reaction event and timeout pattern.

A common cart-recovery design is:

1. receive the cart event;
2. wait for purchase reaction up to a defined timeout;
3. if purchase arrives, end or send confirmation;
4. if it does not, continue to the reminder.

By contrast, “wait two hours, then evaluate the current profile state” is valid when latency and data availability permit. These are different mechanics.

Race conditions and data readiness

Even after time elapses, downstream data may not be ready. For example, a source event, ingestion, Profile update, and audience membership update may occur on different pipelines. Base the timing on documented processing and observed operations, not an arbitrary universal buffer.

If a calculated target date is already past or malformed, do not rely on assumed behavior. Validate the expression and test that case in the current product. Supply a fallback path or prevent ineligible profiles from entering.

Design examples

Relative nurture: Wait three days after signup, then send lesson two. Duration is appropriate.

Appointment reminder: Use a custom calculated date based on appointment time minus 24 hours, with time-zone and missing-value handling.

Engagement optimization: Let send-time optimization choose within an approved window, while honoring campaign deadlines and consent.

Behavioral response: Wait for a purchase reaction with a timeout, rather than sleeping for two days and calling the sleep an event listener.

Verification checklist

• Confirm mode and source fields.
• Keep the maximum at or below 90 days.
• Calculate total path duration within 91 days.
• Verify journey and profile time-zone behavior.
• Test daylight-saving and missing time-zone cases.
• Check reentrance and message pressure during long waits.
• Make the timeout or invalid-date outcome explicit.
• Monitor profiles remaining in waits after publication.