Flow runs and metrics
Who is inside a flow, what each person is waiting for, how it ended, how to cancel a run and how to read the metrics: how many start, how far they get and where they drop.
Every time a person enters a flow, a run is born: that person’s path through that flow, with the version it started with. Each flow’s Runs tab lists them, and Flows → Runs shows the ones for the whole organization, with a filter by flow.
What each run tells you
Above the table you filter by status: All, Running, Waiting for a reply, Waiting for time, Waiting for an event, Finished and With problems. Each row shows its status, who it runs on (the person’s name and the last four digits of their phone), which block it is in (by its name), what started it, how long ago it started (with the exact date on hover) and its latest update.
- Waiting for a reply, Waiting for time, Waiting for an event or With the assistant: it is alive, waiting for that.
- Finished, with its reason: Reached the end, A wait expired, Moved to another flow or The person asked to leave (a word to leave).
- Failed: it ended with an error.
- Cancelled: Cancelled by hand, Cancelled by the flow or Cancelled by the platform.
- Stuck: it is alive but was waiting for something that did not arrive more than ten minutes ago.
A run’s details
See details opens the run: Where it is (the block, what it waits for and until when, what started it and the version), Its path (each step with its time) and What it knows about the person, the variables it collected. This is personal data: do not copy it outside the platform.
- Open the conversation takes you to the thread in the inbox; if the run is about a contact without a conversation, See in Contacts opens their record.
- Cancel the run takes the person out of the flow: the conversation goes back to whoever was handling it and no message is sent. It needs the Flows · operate permission.
The step log is kept for 90 days.
Metrics
The Metrics tab shows how the flow is doing over 7 days, 30 days or 90 days, for All versions or a single one. It comes from the same step log: there are no estimated numbers.
- The cards: Started, Reached the end, A wait expired, Ended with an error (each percentage with its part and its total, “351 of 398 that finished”), Handed to a person (with how many out of those who started) and AI cost. A card with no data does not show: if the flow has no block that assigns to someone, there is no handed-to-a-person card.
- How far they get: a funnel over those who started. With no stages chosen it uses the questions along the path —how many people answered each one— and closes with those who reached the end; with Choose stages you mark up to 6 blocks and it counts how many reached each one. If the stages barely change, instead of equal bars it asks you to choose others.
- Where people drop: the blocks with the most failed actions, runs that ended in error, people who did not reply in time or cancelled runs, with the most frequent reason in words (“The 24-hour window had expired”).
- The path: the flow drawing with how many different people went through each block (darker, more people); Start shows those who started. See as a table shows the same with each block’s waits and average wait.