Did You Know? Nested Branches in a Journey Have a Limit

Sometimes a journey looks perfectly fine on the canvas… until publish time.

One of those easy-to-miss design limits in Customer Insights - Journeys is nested branching. If a journey goes too deep with branch-inside-branch logic, it will not publish and will return an error just like the one below:

Why this matters

Journey logic tends to grow gradually.

What starts as one simple condition can quickly turn into a chain of checks for market, language, consent, audience qualification, product, engagement, or timing. On the canvas, it may still look manageable. Behind the scenes, though, the structure may already be too deeply nested.

What is a nested branch?

A nested branch is exactly what it sounds like: a branch placed inside the path of another branch.

So instead of several conditions sitting at the same level, the logic becomes layered like this:

Important thing to know

This is not really about the journey being “big.”

A journey can be large and still work well if the logic is organized cleanly.

The issue is the depth of the logic, not just the overall number of tiles. A journey with too many conditions layered inside one another can hit the nesting limit even when the rest of the design is reasonable.

What to do instead

When branching starts to stack too deeply, these are usually the best ways to simplify it:

1. Flatten the logic

Look at whether every check truly needs to sit inside the previous one. Some decisions can often be evaluated at the same level instead of being nested.

2. Move qualification logic outside the journey

If part of the branching is really audience qualification, it may belong in the segment rather than in the journey itself.

3. Reposition the last branch or two

Sometimes the fix does not require a full redesign. You may be able to break the nesting by moving the last branch or two lower in the journey or restructuring them a few levels down, as long as the intended customer flow still works the same way.

4. Split the journey into smaller pieces

If one journey is trying to cover too many layered scenarios, that is often a sign it should be broken into separate journeys with clearer responsibilities.

5. Review structure before publish time

The canvas can sometimes hide how deep the logic really is. A quick review of branch depth before publishing can save troubleshooting time later.

A good design check

When the journey starts looking like branch inside branch inside branch, it is worth stopping and asking:

Am I still designing one journey, or am I trying to fit multiple journeys into one canvas?

That question usually points to the right next step.