.svg)
A complex Braze Canvas workflow is one where users take different routes depending on who they are, what they do and how long they wait. Automating it well means choosing the right branching step for each decision, giving evaluations time to settle, and setting exit rules that match your delays. This guide sets out the documented behaviour and the sequencing choices that follow from it.
Key Takeaways
- Decision Split and Audience Paths evaluate the user as they are now, while Action Paths watch for actions across a window of up to 31 days.
- An Audience Paths step needs a delay in front of it when its criteria depend on an interaction with the previous message.
- Ranking decides whether the first action wins or every user waits for the full window, so settle it before launch.
- A user in a Delay step stays there after an exit event until the delay ends, and then leaves the Canvas.
- We recommend drawing the exit rules and a dated timeline before you place the first branch.
What makes a Braze Canvas workflow complex?
A Canvas becomes complex when it holds more than one decision about the same user. Users enter either on a schedule or through an action-based trigger, and from there the steps run in sequence. The first step happens before the second can.
Complexity rarely comes from the number of steps. It comes from branches, waits and exit rules acting on each other. A change to one alters what the others mean.
The practical test is whether you can say, for every step, what a user must have done or been to arrive there. Braze documents the building blocks well, and the pages are linked in the sources below. What the documentation can't tell you is the order in which to make your choices.
Which branching step should you use: Decision Split, Audience Paths or Action Paths?
Each branching step answers a different question. The timing of its evaluation decides which one fits. The table sets out the documented behaviour side by side.
| Step | What it decides on | When it evaluates | Documented detail to plan around |
|---|---|---|---|
| Decision Split | A yes or no test using a segment or filter | Right after the previous step, unless you add a delay | Retargeting filters read all entries, including prior ones |
| Audience Paths | Current attributes and segment membership | At the moment users reach the step | First match wins, order is fixed after launch, up to eight audience groups |
| Action Paths | Actions users perform | Across an evaluation window of up to 31 days | First qualifying action decides the route unless ranking is on |
Read the table as a question about time. Decision Split and Audience Paths look at the user as they are now. Action Paths watch what the user does over a period.
We recommend writing the question each branch asks in one plain sentence before you place it. If the sentence needs the word "and", you probably want two steps in a row, not one clever one.
Why does an Audience Paths step need a delay in front of it?
Audience Paths evaluate immediately. Braze documents that it's important to add a delay before the step if the path criteria depend on a user interaction with a previous step. Without one, users reach the evaluation almost as the message sends.
Everyone then lands in the group for people who haven't interacted. The documentation gives a 24-hour delay as an example, which gives users 24 hours after the message sends to interact before evaluation. The right length for your Canvas is a design choice about how long a reasonable person takes to respond to that message.
This is the failure mode we'd check first in any review. Picture a Canvas that sends an email, branches on whether it was opened, then sends a different follow-up to each group. It looks sound on screen, yet every user reaches the branch before they've had time to open anything.
If the branch depends on something a user does, the better fit is often an Action Paths step. Braze notes that Audience Paths don't evaluate the specific event that triggered Canvas entry. Routing by actions users perform belongs to Action Paths.
Two more documented behaviours matter here. Users stay in the audience group they were placed in even if their profile changes afterwards. A delay, quiet hours or rate limiting can sit between the branch and the message, so turn on audience validation in the Message step's delivery validations to confirm users still qualify at send time.
How does ranking change what an Action Paths step does?
With ranking off, the first qualifying action decides the route. A user who performs a second action that matches a different group doesn't switch paths. Anyone who performs no trigger event goes down the Everyone Else group when the window ends.
With ranking on, all users are held until the end of the evaluation window. Then each user advances through the highest priority group they qualify for. The evaluation window defaults to one day and the maximum is 31 days.
The choice is about speed against priority. Ranking off suits a follow-up that should go out soon after the action. Ranking on suits a case where several outcomes are possible and one clearly matters more, but every user then waits for the full window.
Decide this at design time. Braze advises against changing the ranking setting after launch while users are already in the step, because path state recorded earlier in the window may reflect a previous setting.
One detail applies to in-app messages. When the trigger is starting a session and the next step is an in-app message, the user must perform two session starts to receive it.
What happens to exit criteria when a user is in a delay?
Exit criteria remove users from a Canvas when they perform an exception event. Braze marks the user to exit immediately, and the user doesn't advance to any later step. A user sitting in a Delay step stays in that step until the delay period ends.
The documented example is a Delay step of 30 days. A user who performs the exit event on the first day is marked to exit right away but doesn't fully leave until the Delay step ends 29 days later. If your reporting reads exits from the Canvas, expect it to reflect that gap.
For long waits, we recommend setting the exit criteria first and the delay second. The aim is that a user who has already done the thing you're nudging towards never receives the next message.
Plan for one documented gap: array attributes aren't currently supported as exit criteria on exception events. A journey that depends on one needs a different exit signal.
Which delay settings cause users to leave a Canvas unexpectedly?
Delays are where timeline mistakes hide. A Delay step can run up to two years (730 days), which makes it easy to build a journey whose dates stop making sense. Several documented behaviours remove users from the Canvas.
- If a chosen date and time have already passed when users reach the Delay step, users exit the Canvas.
- For "wait until an exact day" steps, there can be up to 31 days between Canvas start and the chosen dates.
- If a Canvas has two Delay steps and the first is longer than the second, users exit the Canvas.
Also note the difference between a day and a calendar day. A day is 24 hours from the moment the user enters the Delay step. A calendar day waits until the next specified time, which could be less than 24 hours.
Before building, sketch the timeline on paper with real dates. Mark where each delay starts and ends, and check that no later delay falls inside an earlier one. It's a small job that heads off a class of unexpected exits.
When should you use Canvas Context in a complex workflow?
Context steps let you create and update variables for a user as they move through a Canvas. These variables exist only for that Canvas journey, and you can define or update up to 10 context variables within a single Context step. Each Canvas entry redefines them from its own entry data, so a user can have several active journeys with separate context.
That makes Context a good fit for data that belongs to one entry, such as a booking, an order or a renewal date. It's a poor fit for anything you want to persist beyond the journey. Availability varies by workspace, so confirm it in yours before you design around it.
How would a hypothetical Canvas come together step by step?
Take a hypothetical subscription business that wants new members to choose a delivery preference. This is an illustration of the sequencing advice above, not client work and not delivery data. It deliberately uses no figures.
- Set the entry as action-based, triggered by the sign-up event. Add the preference-chosen event as an exception event in the exit criteria. Anyone who completes the task then stops receiving nudges.
- Send a welcome message, then place an Action Paths step with ranking off. The group for users who start a session gets a quick follow-up, and everyone else waits out the window.
- For the quick follow-up group, use a Decision Split on channel eligibility. Users who can receive push get a push, and the rest get an email.
- On the Everyone Else path, add a Delay step long enough for a reasonable person to have responded, then an Audience Paths step. Order the groups with the highest-value audience first, because users take the first path they qualify for.
- Turn on audience validation in the Message steps that follow any wait, and draw the dated timeline before launch.
What the example shows is the order of decisions. Exit rules come first, then entry, then the branching choice that matches each question, then the delays that give each evaluation time to settle.
How do you check a complex Canvas after launch?
Plan the checks before you launch. Braze recommends setting the conversion window to at least match the longest path in the Canvas.
A release note dated 15 Oct 2026 lists Messaging Observability with a status of ga. It describes tracing events across a Canvas or campaign so you can audit entries, suppressions, failures and sends in one place. If you have access, it's a natural place to look when a branch sends fewer messages than you expected.
How does this connect to the rest of the programme?
A complex Canvas sits inside a wider programme, and the posts below cover the neighbouring decisions. Our guide to automating an onboarding journey in Braze Canvas applies these patterns to a first-run flow. For channel-specific builds, see how to automate mobile campaigns in Braze Canvas.
If you're deciding how Canvas fits against other automation, read how to build an automated marketing workflow in Braze. The entry side is covered in setting up engagement triggers in Braze. Connected Content for personalised campaigns covers pulling live data into messages.
Teams that want written rules for how Canvases are built and reviewed can read our post on automated campaign QA with Agentic Standards. Our case study on unifying guest profiles for a hospitality group covers Braze Canvas journeys with an automated fallback across messaging channels, the kind of channel decision in the example above. For the Braze documentation behind this post, start at the Canvas section of the Braze docs.
As a Braze implementation partner, CustomerIK recommends that you draw the exit rules and the dated timeline of a complex Canvas before you place its first branch. Doing so makes the later choices about branching and delays easier to check.
Frequently Asked Questions
1. What is the difference between Audience Paths and Action Paths?
Audience Paths route users by their current attributes and segment membership at the moment they reach the step. Action Paths route users by actions they perform during an evaluation window.
2. How many audience groups can an Audience Paths step hold?
Braze documents up to eight audience groups per Audience Paths step, and you can connect several Audience Paths steps to sort users further. Group order is fixed after launch.
3. How long can an Action Paths step wait for an action?
The default evaluation window is one day. The documented maximum is 31 days.
4. How long can a Delay step last?
Delay steps can run up to two years (730 days). A Delay component can connect to no more than one subsequent step.
5. Do users leave a Canvas straight away when they hit an exit event?
Braze marks them to exit immediately. If they're in a Delay step they stay there until the delay ends, and then leave without advancing.
Sources
- Braze, Canvas basics. Retrieved 23 Oct 2026.
- Braze, Audience Paths. Retrieved 23 Oct 2026.
- Braze, Action Paths. Retrieved 23 Oct 2026.
- Braze, Decision Split. Retrieved 23 Oct 2026.
- Braze, Exit criteria. Retrieved 23 Oct 2026.
- Braze, Delay step. Retrieved 23 Oct 2026.
- Braze, Context step. Retrieved 23 Oct 2026.
- Braze, Release notes. Retrieved 23 Oct 2026.
- Written by CustomerIK, a Braze implementation partner.
CustomerIK is a Braze implementation partner working across onboarding, technical integration, marketing operations and customer data management.
If you're planning a Canvas with several branches and long waits, let's talk.
.svg)
