Wait tiles and trigger timeouts

What it does

Wait tiles hold a customer at a point in the journey. There are two kinds: a plain wait that pauses for a duration or until a date and time, and a wait-for-trigger tile that pauses until something happens and branches on whether it happened before the timeout expired.

Key facts

The plain wait tile has two modes: a set amount of time (the clock starts the moment the customer reaches the tile), or until a specific date and time.
If the target date and time on a wait tile is already in the past when the customer arrives, they pass straight through rather than being held or dropped.
Maximum wait is 90 days — twelve weeks — however you configure it. The same 90-day ceiling applies to every timeout on a wait-for-trigger tile.
The wait-for-trigger tile is strictly two-way: a yes path when the condition is met inside the window, a no path when the timeout expires. There is no third outcome.
It has three condition types: wait for an interaction with a previous message (opened, clicked, and the SMS and push equivalents), wait for the customer to become a member of a dynamic segment, and wait for a trigger attribute to reach a specific date and time.
Customers move to the yes path immediately on the condition being satisfied — they do not sit out the remainder of the window.
Wait for segment membership does not support Customer Insights - Data segments built on a bring-your-own-storage-account setup.
The date-and-time variant needs the date to be carried on the trigger that started the journey; it can't read an arbitrary field at runtime.
The message series tile is the other time-based construct: it steps through a sequence of messages until an exit condition is met, a time limit is reached, or the steps run out.
Attribute branch tiles evaluate on arrival and support multiple paths, which is the alternative when a two-way wait isn't enough.

When to use / skip

You will use wait tiles in almost every journey, so the real question is which one. Use a plain wait when the timing is the point — hold three days before the reminder, hold until the webinar starts. Use wait-for-trigger when the behaviour is the point and the time is just a deadline.

Where people over-engineer is chaining waits to build long nurture programmes: a 60-day sequence stitched from six wait tiles is brittle, hard to change, and produces analytics nobody can read. If the customer's state changes over that period, a shorter journey re-entered by a trigger is usually the better shape.

The 90-day ceiling quietly rules out a category of requirement — annual renewals, birthday-minus-one-year, "check back in six months". Those need a scheduled segment journey or a Dataverse trigger on a date field, not a wait tile. Establish that early, because clients ask for it more often than you'd expect.

Configuration decisions

Plain wait versus wait-for-trigger at each pause: is the deadline the point, or is the customer's action the point?
The timeout value on every wait-for-trigger tile, and what the no path actually does. A no path that just ends the journey is usually a wasted opportunity, and sometimes a wasted licence cost.
Whether long delays belong inside one journey or across two journeys joined by a trigger — this decides how readable your analytics are.
Which interaction you are actually waiting on. "Opened" is a weak signal on modern mail clients with image proxying; clicked is the one that means something.
Time zone handling for date-and-time waits, which follows the journey's time zone unless the design says otherwise.
Whether the wait window and the quiet-times window overlap, because that determines when messages really land.

Gotchas

Everything is capped at 90 days. There is no override, and the designer lets you build the flow before telling you.
A wait-for-trigger tile with a 30-day timeout keeps that customer in the journey for up to 30 days. Editing the journey in the meantime creates a new version and those people stay on the old one.
Waiting on "email opened" produces optimistic yes paths on some clients and silent no paths on others. Privacy proxies pre-fetch images. Design branches so the no path is not punitive.
Wait-for-segment-membership evaluates against segment refresh, so the customer moves when the segment updates, not the instant their data changes.
A past-dated wait tile passes the customer through with no delay and no warning. On a journey published late, that can fire the whole sequence at once.
Stopping a journey drops in-flight customers wherever they are, including mid-wait. Their remaining steps are skipped and cannot be resumed.

Consultant notes

Draw the timing on a whiteboard with real dates before anyone opens the designer. Wait tiles are where journey designs quietly become impossible.
Tell the client the 90-day limit in the first design session, not when you hit it. It reframes annual and lifecycle campaigns as multiple journeys, which is the right answer anyway.
Demo the yes/no split on a wait-for-trigger tile with a real email — it is the moment marketing users understand why this is not a mail merge tool.
Before go-live, walk every no path and check it does something sensible. Half-finished no paths are the most common review finding.
Check whether long waits interact with the client's data retention or consent withdrawal processes; someone sitting in a wait tile for 89 days may have unsubscribed on day three.

Worth another look if the 90-day wait ceiling ever moves, or if multi-way wait tiles arrive.