Skip to content

Commit 97f896e

Browse files
committed
explain how delay works
1 parent acce8a6 commit 97f896e

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

src/engage/journeys/event-triggered-journeys-steps.md

+11
Original file line numberDiff line numberDiff line change
@@ -107,6 +107,17 @@ Deleting a Hold Until step can impact downstream steps that rely on it. When you
107107

108108
The **Delay** step holds profiles in a journey for a set period before they can proceed to the next step. This enables controlled timing for messages, actions, or other journey events.
109109

110+
### How Delay works
111+
112+
When a journey reaches the Delay step:
113+
114+
1. Profiles enter the step and wait for the configured duration.
115+
2. Segment logs the profile's status in the observability timeline.
116+
3. If an exit condition is met during the hold period, the profile leaves the journey early.
117+
4. After the delay ends, the profile moves to the next step in the journey.
118+
119+
120+
110121
## Send to Destination
111122

112123
The **Send to Destination** step lets you send journey data to one of your [configured Engage destinations](/docs/connections/destinations/), enabling real-time integration with tools like marketing platforms, analytics systems, or custom endpoints.

0 commit comments

Comments
 (0)