This article explains a UI rendering limitation in Journey Builder Test Mode where the visual pathing may not accurately reflect the contact's route. This is a visual-only discrepancy and does not impact data processing.
In Test Mode, contacts moving through a Decision Split directly into a Join activity may not have their specific branch path highlighted on the canvas.
The UI display in Journey Builder's Test Mode is designed to render the path to the next activity executed by each contact. If a Join activity is placed immediately after a Decision Split, the system internally retains the information of the next activity to be executed. However, the UI rendering of which branch path was taken to reach the join point may not reflect the correct route.
This issue is a limitation within the Test Mode UI display. In actual processing after activating the journey, the Decision Split is correctly evaluated based on the configured conditions. Contacts pass through the route that meets the conditions and proceed to the processes after the Join activity, so there is no impact on data processing in actual operations.
To visually verify contact routing in Test Mode, implement one of the following methods:
・Place another activity between the Decision Split and the Join activity: Place a Wait activity (e.g., 1 minute) between each branch of the Decision Split and the Join activity. This allows the UI to render the path from the Decision Split to the Wait activity.
・Adjust the Decision Split configuration: Review the condition settings of the Decision Split and the placement of activities so that the intended processes (such as Email sends) can be performed without using a Join activity.
・Accept as a display-only limitation: Since there is no impact on actual processing, proceed to activate the journey as-is, acknowledging that the UI display is incorrect.
005317380

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.