Skip to main content
The flow run statistics report shows you how customers move through a flow, where they exit, and how each block performs. Use it to verify expected volumes, identify drop-off points, and surface ideas for improving mechanics. In flow run statistics you can view:
  • How many customers entered the mechanic
  • How they distributed across branches and at which blocks they ended their run
  • The most frequently occurring execution errors
  • Metrics on sent campaigns

​
Why use this report

The run statistics report helps you:
  • Verify that the expected number of customers pass through the flow
  • Adjust settings that cause unnecessary customers to exit the flow
  • See how parallel flows affect each other and your target metrics
  • Find growth opportunities and build hypotheses to improve your mechanics

​
How to view run statistics

The Runs mode is enabled automatically when you open a flow. The successful runs count is displayed next to each block for the selected period. Wait blocks show paused runs, and the start block shows the processing queue at the end of the selected interval (or at the time the version was stopped if it was edited that day).
Statistics are available for the last 30 days within the open version.
Only those who entered the flow during this period — counts only runs that started inside the specified timeframe for the open version. This excludes runs of customers who were already sitting in wait blocks at the start of the period, as well as runs carried over from previous versions. Values are shown both as absolute numbers and as a percentage of the first block.

​
Detailed block information

Click a block to open run details:
  • Number of entries
  • Number of transitions (broken down by branches when the block splits)
  • Number of unique customers from the transitions
  • Stop reasons
The displayed values depend on the block type.

​
Event-based start

  • Entered the flow and awaiting processing (only when customers are in queue)
  • Entered the block
  • Moved to the next block
  • Filtered out (customers did not meet the block conditions)

​
Schedule-based start

  • Did not enter the flow due to frequency settings
  • Entered the flow and awaiting processing (only when customers are in queue)
  • Entered the block
  • Moved to the next block

​
Condition

  • Entered the block
  • Moved to the “yes” branch
  • Moved to the “no” branch
  • Exited the flow (in blocks without a second branch)

​
Split

  • Entered the block
  • Moved to branch 1, 2, and so on

​
Wait

  • Total entered
    • Entered during this period
    • Entered during previous periods
  • Currently in block
  • Moved to the next block

​
A/B test

  • Entered the block
  • Moved to Variant 0, Variant 1, and so on

​
Limit

  • Entered the block
  • Moved to the branch before the limit was triggered
  • Moved to the branch after the limit was triggered
The counter value and the number of transitions to the “before limit” branch can differ for two reasons:
  • The counter counts only runs in which at least one step group after the limit executed successfully. “Moved to branch” counts every exit from the block toward that branch.
    For example, if a step group after the Limit block fails with an error and does not execute, the block exit is counted but the limit count is not.
  • The limit counts globally across all versions and resets only on a manual reset or when the limit is edited. The values in Runs reset every time a new version is launched.
    For example, if you edit a flow but change nothing in the Limit block, block exits drop to zero while the limit count stays the same.

​
Step group

  • Entered the block
  • Steps executed

​
Statistics on sent campaigns

In Step group blocks that send campaigns, the Settings tab shows metrics pulled from the campaign report.
Report limitations:
  • Statistics are shown with date precision only and are not tied to hours. Different flow versions running during the selected period will show identical campaign metrics.
  • Data is pulled from the campaign, not from messages sent by a specific block. If the same campaign is used in multiple branches or flows, statistics for the same period will be identical.

​
View and export customers from a branch

On the Runs tab, the Show customers button lets you:
  • View up to 10 unique recent customers and their runs
  • Download the complete customer list
  • Add all customers to a segment
Customers appear in the list if they:
  • Moved to a specific branch in a branching block (condition, split, A/B test, limit)
  • Executed steps in a step group
  • Exited the flow due to a stop
Clicking the button next to a customer opens the tab with that customer’s run history.
Deletion and merging. Run records for deleted customers are preserved, but viewing them is unavailable. The same applies to non-primary customers in a merge who lose their Maestra Id.

​
Export

Click Export to create a task. The finished file contains a list of MaestraId values. Customers can also be exported through the API.
The file may contain more customers than you saw in the UI if new runs occurred while you were reviewing the details. Export pulls data that is current at the moment of download.

​
Add to segment

When flow errors cause customers to take the wrong branch or exit the flow incorrectly, use the Add to segment function. Select the static segment to add customers to. If no suitable segment exists, create one first. To monitor the import results, follow the link to the task.

​
Stop reasons

A stop means a run was interrupted at one of the blocks. The canvas shows the total number of stops for the selected period. Click the count to open a list that groups stops by block and shows reasons, counts, and the last ten affected customers for each reason. The same information appears on the block tab. Stops related to flow frequency settings are also shown there.

​
Report usage examples

​
Example 1

Task. Develop hypotheses to increase revenue for the “Price on a product in Favorites decreased” mechanic. Analysis. The flow report shows that only 77% of customers matching the event reach the campaign send step. Customers exit at the contact check stage. Check customer contacts in other channels — some customers unsubscribed from email but use the app and are subscribed to push notifications. Solution. Adding mobile push subscribers to the flow increases the mechanic’s reach from 76.85% to 96.3%.

​
Example 2

Task. Determine why the mechanic’s effectiveness dropped compared to previous periods. Analysis. The report shows that the second email reaches 49% of customers in the sequence (it is sent three days after the first email if the first one is not opened). But the open rate on the first campaign is around 30%, so the second email should reach far more customers. Check the transitions on the “no” branch. The customer does have an open of the first campaign, but it was more than six months ago, during a previous run of the sequence. The flow filter has too strict a condition and excludes valid customers. Solution. In the Condition block, specify that opens should be absent only for the last three days (counted from the start of the current run). Customer distribution across branches becomes correct, and all eligible customers receive the second campaign in the sequence.