DocumentationJourney OrchestrationJourney Orchestration

Wait activity

Last update: Wed Jul 27 2022 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Intermediate
  • User

If you want to wait before executing the next activity in the path, you can use a Wait activity. It allows you to define the moment when the next activity will be executed. Three options are available:

About the Wait activity

Here is how waits are prioritized when you use several waits in parallel. If they have the same time configuration and a different but overlapping condition, the wait positioned above will be the one prioritized. For example, the condition of the first wait is “being a woman” and the condition of the second wait in parallel is “being a VIP”. The first wait activity will be prioritized.

Also note that if two different waits are in parallel, the one occurring first will be prioritized, regardless of its vertical position. For example, if a 1-hour wait is above and a 30-minute wait is below, after 30 minutes, the 30-minute wait will be processed.

NOTE
The maximum wait duration is 30 days.
In test mode, the Wait time in test parameter allows you to define the time that each wait activity will last. The default time is 10 seconds. This will ensure that you get the test results quickly. See this page

Duration wait

Select the duration of the wait before the execution of the next activity.

Custom wait

This option lets you define a custom date, for example 12 July 2020 at 5pm, using an advanced expression based on a field coming from an event or a data source. It does not let you define a custom duration, for example, 7 days. The expression in the expression editor should provide a dateTimeOnly format. See this page. For more information on dateTimeOnly format, see this page.

NOTE
You can leverage a dateTimeOnly expression or use a function to convert to a dateTimeOnly. For example: toDateTimeOnly(@{Event.offerOpened.activity.endTime}), the field in the event being of the form 2016-08-12T09:46:06Z.
The time zone is expected in the properties of your journey. As a result, it is not possible today from the interface to directly point at a full ISO-8601 timestamp mixing time and time zone offset like 2016-08-12T09:46:06.982-05. See this page.

recommendation-more-help
4f4a00c1-77c9-4eee-84df-bbe6206c3ab9