Skip to main content

​
Overview

Errors in Journey execution are surfaced at the individual node level in the Journey Canvas. The panels described below are the primary interfaces for identifying and diagnosing failures.

​
Accessing the Execution Details Panel

The right-hand Execution Details sidebar is the source of truth for why a specific profile failed at a specific step. How to access it:
  1. Navigate to the failed node in the Journey Canvas.
  2. Open the right-hand Execution Details sidebar.
This panel displays:
  • The Failure Status Code
  • Timestamp of the failure
  • Destination name
  • The Request ID needed for escalations
📸 Screenshot needed: The right-hand “Execution Details” sidebar showing failure context for a specific profile — Failure Status Code, timestamp, destination name, and Request ID. (Loom ref: 03:20)

​
Validating Data Mapping (Field Mapping Screen)

If an error code indicates BAD_REQUEST or EVENT_PARSING_FAILED, the root cause is almost always in the field mapping configuration. How to access it:
  1. Navigate to the destination node’s settings in the Journey Canvas.
  2. Open the Map Your Fields screen.
  3. Inspect and fix the mapping.
📸 Screenshot needed: The “Field Mapping” / “Map Your Fields” configuration screen for a destination node. (Loom ref: 01:22)
Pay special attention to the Primary Identifier field (e.g., external_id or email). A null value here is the cause of 90% of BAD_REQUEST errors.

​
Determining if a Failure is Global or Isolated

Before diving into individual error codes, first determine the scope of the failure — this narrows down the likely cause significantly.
  1. Switch the toggle to Total Users in the Journey analytics view.
  2. Analyse the ratio:
    • If 100% of users are failing at a node → likely an Authentication or Mapping error.
    • If only a small percentage (e.g., 5%) are failing → likely a Consent or Bad Request (data quality) issue.
📸 Screenshot needed: The Journey analytics view with the “Total Users” toggle switched on. (Loom ref: 01:15)

​
Refreshing the Execution View

The Execution view is not always live and may require a manual refresh to reflect recent changes or retry attempts.
  • Use the Refresh icon to pull the latest execution data.
  • Always refresh after making a configuration change before concluding whether the fix was effective.
📸 Screenshot needed: The Refresh icon in the Execution View panel. (Loom ref: 00:30)

​
Next Steps

Once you have identified the error, refer to Journey Error Codes for detailed resolution steps.
Last modified on March 21, 2026