You would think this should be easy. Set a Journey end date, change your mind later, go back in, clear the value, done. Except… not quite. In Customer Insights - Journeys, removing a journey end date is not always as straightforward as you would expect. And that can turn a
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
If you’ve ever hesitated before saving changes to a journey that’s already Live, you’re not alone. In Customer Insights – Journeys, live journeys are designed to keep running while you make changes — but the key is understanding how updates apply and who they apply to. This post is
Quiet time is a delivery control, not a journey-entry control. Contacts can still progress through the journey, but if a message lands inside a quiet-time window, it’s held (queued) and then released when quiet time ends. In one-time journeys with a static audience, you can often reduce the risk
Journeys can translate into an execution plan that hits a hard limit of 500 actions, consistent with Power Automate workflow limits.