---
title: "Architect Journey: Wait Until Dynamic Time"
slug: "architect-journey-wait-until-dynamic-time"
description: "Explains Architect Journey Wait Until Dynamic Time, covering dynamic scheduling, time-based conditions, configuration steps, and journey automation."
tags: ["architect wait", "wait for some time", "wait element"]
updated: 2026-09-23T18:15:37Z
published: 2026-09-23T18:15:37Z
canonical: "academy.insiderone.com/architect-journey-wait-until-dynamic-time"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Architect Journey: Wait Until Dynamic Time

The Wait Until Dynamic Time allows you to pause journeys based on each user’s data instead of a fixed time.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/Screenshot%20at%20Oct%2015%2016-29-28%20(1).png)

You can use this wait element for various cases, such as when your campaign timing depends on events or attributes that differ per user, like a flight date, a product’s expiry, or a show premiere. For example, you can use the dynamic value in event parameters to create a wait element of "3 days before a user's subscription renewal date."

You can use this element in journeys starting with the [On Event](/docs/architect-journey-starter-on-event) or [On Dynamic Date](/docs/architect-journey-starter-dynamic-date) elements.

## Use cases

You can use the Wait Until Dynamic Time element to create more personalized and automated journeys across industries:

- **Ecommerce**: Send replenishment reminders 3 days before users will likely run out of a product.
- **Travel**: Send pre-flight or hotel reminders a few hours before each user’s departure or check-in time.
- **Entertainment**: Notify users just before their favorite show premieres.
- **Fintech/retail:** Remind loyalty users before their tier or offer expires.
- **Beauty/personal care**: Trigger re-purchase nudges before the average product-usage cycle ends.

This feature lets you run fewer, smarter, and more relevant campaigns without manually duplicating journeys for every timing variation.

## How does Wait Until Dynamic Time work?

The Wait Until Dynamic Time connects to a constant event parameter inside the journey's trigger.

Only **date/time** event parameters are supported. Each element can use one parameter at a time.

The analytics of a journey with the Wait Until Dynamic Time element will display the users who are on hold or dropped based on your fallback setup.

### Dynamic date

The journey [waits until the exact timestamp](https://academy.insiderone.com/docs/architect-journey-use-wait-until-dynamic-time) in the event parameter (e.g., flight_date, show_start_time, etc.). You can add an optional shift (e.g., “2 hours before”). If the parameter is **missing** or **invalid**, users will drop from the journey.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/Screenshot%20at%20Oct%2015%2017-57-46.png)

You can build the following example cases using this element.

- **Airlines**: Wait until **flight_date**, shift by “–2 hours,” to send check-in reminders.
- **Streaming**: Wait until **premiere_date**, shift by “–30 minutes,” to send push notifications.
- **Loyalty programs**: Wait until **tier_expiry_date**, shift by “–2 days,” to notify users of pending renewals.

> Refer to [Use an Array of Objects in Journey Elements](/docs/use-an-array-of-objects-in-journey-elements) to use the parameter list that provides the date fields of the object the journey started from, so the journey can wait on a different date than the one that let the user in.

### Dynamic duration

You can configure dynamic duration with the [Wait for Some Time](https://academy.insiderone.com/docs/using-wait-for-some-time) element. The journey waits for the duration defined in a numeric event parameter (e.g., days_until_refill = 30). You can define the unit (hours/days) and add a shift if needed. If the parameter is **missing** or **invalid**, you can drop users from the journey or let users proceed to the next element in a specified duration.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/Screenshot%20at%20Oct%2015%2017-58-19.png)

You can build the following example case using this element.

- **Retail replenishment**: Wait for the number of **days** stored in r**eplenishment_duration** and send a reminder **3 days before** it ends.