Loading

Marketing Cloud Engagement | Journey Builder: Pathing Limitation When a Join Activity Follows a Decision Split

Date de publication: Apr 6, 2026
Description

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.

Résolution

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.

 

Root Cause

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.

 

Production Impact

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.

 

Workarounds

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.

Numéro d’article de la base de connaissances

005317380

 
Chargement
Salesforce Help | Article