Once a scenario is active, the Insights view shows exactly how it's doing: not only totals, but per-step metrics overlaid on the flow itself, and a full record of every individual run.

Open it from inside the builder with Results in the top-right corner, or from the Scenarios list by hovering a scenario and choosing ⋯ → View history.

Any number that isn't zero is clickable. Click one and a panel opens with the exact contacts it counted, so you can go from "47 converted" to who those 47 people are without building a filter. This works on the summary stats and on the per-step numbers in the flow below, which is the fastest way to investigate a drop-off: click the step before it and the step after it, and compare who's in each list.

The left panel shows the top-level numbers:

A conversion is counted whenever a step in the run records one. The most common source is a conversion-link click; every click on a conversion link counts as a conversion. Survey completions and payments can count too.

The right panel shows your flow as read-only nodes with metrics on each one. This is where the real detail lives.

Reading top to bottom gives you a funnel. Where the numbers drop sharply between steps is where contacts disengage, so that's the step to work on. Click any number to see the list of people behind it.

The History tab is a record of every individual run of the scenario.

Each row is one run: one contact going through the scenario. A row shows the contact's name and handle, folder tags, a timestamp, a status, and a Test badge for test runs.

In the builder, History in the top bar shows the same runs in a panel beside the canvas, on a computer. See The Flow Builder: Visual Editor Tips & Tricks.

Click a row to open the run on the flow. Each step shows its status and what it did for this contact: the text that went out (with variables filled in), the folders the contact was Added to or Removed from, the value a property was set to, whether the contact opted in or out, and the Checked value of a condition. Branches the run didn't take are faded. If an AI condition ran while you had no AI credits left, the step says it wasn't evaluated. A step still waiting has a Cancel button, and a failed one has Retry. Click the contact card to open their conversation.

Filter the list by status, search by contact, and pick a date range. The statuses are Pending, Completed, Partially completed, Failed, Interrupted, Limit reached, Disconnected and Paused by Instagram. Turn on Needs attention to see only the runs that failed, partially completed, reached the limit or were disconnected.

A run is Partially completed when a step fails after at least one other step worked. Each row shows a line of icons, one per step in order; hover one to see the step, its status and date, and the error if it failed.

Three statuses mean a run was held instead of finished:

A held run started by a comment becomes Expired after 7 days, because Instagram allows a private reply to a comment for 7 days only.

When a step fails, you can retry it. In the Insights flow a node with failed runs offers a retry control, and in the History tab you can retry an individual run. This re-runs the step and continues the flow from there. To retry every failed run of a step in one go, click the ⋮ menu next to the step's Failed count and choose Retry all failed; it's the quickest fix after a temporary problem. Inrō already retries unexpected errors a few times on its own before marking a run as failed, so a failed status usually means something needs your attention.

Start in the Insights tab and scan the flow top to bottom. Look for a step where the sent number drops sharply against the step before it. A big drop means contacts aren't reaching that step, either taking a different branch or not converting on the previous one.

For message steps, compare sent to read. A low read rate on an early message usually means the DM isn't being opened at all. For conversion links, compare sent to clicked; a low click rate usually points to the card design or the timing of the ask.

When you find a weak step, open the History tab and read a few real runs around it. The fix is often obvious once you see the actual conversation.

If the flow looks healthy but too few people are entering it at all, the automation isn't the problem: look at the post instead, in Your Instagram Content in Inrō. For one-off sends rather than automations, see Campaign Metrics & Performance Tracking.

You can now build, run, and optimise scenarios. To send proactive outreach to a chosen audience instead of waiting for a trigger, read What Are DM Campaigns?. To revisit the canvas, see The Flow Builder: Visual Editor Tips & Tricks.