Review Path History
Updated 2 months ago
.
Review Path History
Inspect journey runs, outcomes, branch paths, and step-level history for people who entered a journey.
Use Path History when you want to understand what happened after donors, trip participants, or recipients entered a journey. It is the best place to answer questions like "Did this person receive the message?", "Which branch did they take?", and "Where are they waiting now?"
Path History tab with recent journey runs, statuses, branches, current steps, message counts, and inspect actions.
Review recent runs
Open the journey.
Choose Path History.
Review the summary metrics.
Search the current page when you need to find a record, branch, step, or exit reason.
Select Inspect on a row when you need the full workflow history for one person.
The summary metrics show:
Entries: Total recent records shown for the journey.
Active now: Records still moving through the journey.
Completed: Records that reached the end of the journey.
Exited early: Records that left before normal completion.
The table shows the record, status, branch, current or last step, messages sent, exit reason, and entry date.
Inspect one journey run
Use the inspect drawer when you need to diagnose one person's path through the journey.
Path History inspect drawer with workflow path, current wait state, execution timeline, and message evidence.
The drawer can show:
the record's current journey status,
the branch taken,
messages sent,
the current or last step,
the exit reason,
the workflow path,
the execution timeline,
step details such as message channel, subject, template, wait time, or branch result.
Use the drawer tabs to move between workflow details, outcomes, alerts, and bottleneck information when those sections are available for the run.
Interpret common statuses
Use the status and exit reason together.
Active means the record is still in the journey. The current step may be a wait, message, task, branch, or another action.
Completed means the record reached the normal end of the journey or achieved the configured goal.
Exited early means the run stopped before the normal ending, such as when a branch did not match or a step failed.
Failed means the journey could not complete a step and needs review.
Diagnose journey health
Use Path History together with the health indicators on the Journeys overview when you want to decide what needs attention.
Review a journey when you see:
recent step failures,
missing message content,
a branch with no matching path,
people waiting longer than expected,
no recent entries for a journey that should be active,
a notification or task step that does not have enough detail.
If the issue is with an active journey's structure, duplicate the journey to create an editable draft, make the correction, and publish the replacement when it is ready.