Skip to main content

Use Step Reports to Track and Troubleshoot Journey Runs

See what happened to every account, person, and signal at each step of a Journey run, review errors, download records, and rerun failures.

Step reports show you what entered each step of your Journey, what came out, and what happened to every record in between, so you can find the exact point where a run went off track.

What a step report shows

Every step on the Journey Canvas displays its input and output counts for the run. Click any step to open a panel with two tabs: Summary and Report. The Report tab shows the input and output counts at the top, followed by the Step Events list: every account, person, or signal processed at that step, with its Processed Date and Processing Status.

The report shows only the steps you built. Behind-the-scenes processing, such as staged evaluation of dependent computed attributes, rolls up into the step you created.


Open a step report

  1. Go to Journeys and open your Journey.

  2. On the Canvas, review the input and output counts shown on each step.

  3. Click a step and open the Report tab.

  4. Use the gear icon above the list to choose which columns to display.


Understand record statuses

Each record in a step report carries a Processing Status:

  • Success: the step processed the record and passed it to the next step.

  • Warning: the step hit an issue but still passed the record forward. Enrichment steps work this way: if a lookup fails, the record continues through the Journey without the new data.

  • Error: the step could not process the record. For example, an enrichment step that finds no data for an account marks it as an error.

  • To be processed: the record has entered the step but has not been processed yet.

  • No Branch Match: on branch steps, the record matched none of the defined condition paths. Records that did match show their branch in the Condition Path column.

The report header also shows total events next to each count. A record generates a new event each time the step processes it, so if the same account flows through on two different days, it counts once as an account and twice in events.


Review errors faster

Filter the record list by Error status to jump straight to the records that failed, instead of scanning the full list. For Signal-based steps, the report shows full Signal details for each record, so you can see exactly what data the step was working with.


Export records

At any step, export the input or output records with all their columns. Click the download icon in the Report tab and choose Export Input or Export Output for the entity at that step (Accounts, Persons, or Signals).

Exporting both sides of a step is a quick way to see its exact effect. On a step like Filter Valid Emails, export the input persons and the output persons and the difference is the list of records the filter removed.

Use exports to audit enrichment coverage, share a snapshot with your team, or work with a step's output outside Tapistro.


Rerun failed records

Use Rerun Errors on a step to reprocess only the records that failed, without rerunning the whole Journey. If the step writes a computed attribute that depends on other attributes, Tapistro re-evaluates the dependencies first, so recovered records get fresh values end to end.


Tips

  • Compare input and output counts step by step across the Canvas. The first step where the count drops sharply is where to start your review.

  • If counts drop right after your Sources, check whether two Sources are feeding the same records. Tapistro deduplicates them, so the combined count shrinks at the next step.

  • A Warning is not a failure. The record kept moving. Reserve your attention for Errors, which stop a record at that step, then use Rerun Errors once you fix the cause.

  • Before an Activation step, export the output of your last enrichment step and check coverage. It is faster than discovering gaps after outreach starts.

Did this answer your question?