See exactly what your flow did
A flow's run record now lights only the route it actually took — from the trigger that started it — and every step can be opened to show what it received, what it used, and what came back.
Released 23 August 2026
When a flow does something you did not expect, the run record now tells you exactly where it went and why.
What's new
- One route, lit. A step with two outcomes — Success and Couldn't find that chat — used to draw both connectors as live, which told you nothing. The run record now lights only the branch the run actually took.
- Including where it came in. The trigger that started the run is lit too, with the connector into the first step. On a flow with a trigger per channel, you can see which one actually brought the run in — and in the builder's Stats overlay, how many runs each trigger has started, so you can tell which are pulling their weight.
- Open any step. Click a step to see what it received, the settings it used after your
{{variables}}were filled in, and the result that came back — plus whether a message was delivered. This is usually the whole answer: the resolved value shows you why a step branched the way it did. - Search inside a step. Each section has its own search box, so you can type a field name or a value instead of reading down a long list.
- See what started the run. The details that triggered the flow are shown at the foot of the timeline.
- More room for the canvas. Fold the details panel away to see the whole flow; your place is remembered. The step panel in the flow builder folds away the same way.
- Search the step tray. In the builder, type to find a step by name across every tab, instead of working out which tab it lives under.
Worth knowing
- Older runs improve too, mostly. For runs that finished before this update, the record works the route out from which steps ran: if only one connector could have led to a step that ran, that is the one taken. Where two outcomes of a step lead to the same next step, neither is lit — we would only be guessing. New runs record it exactly.
- A new flow starts from a recipe. Choosing New flow offers a few ready-made starting points — a welcome and menu, capturing a lead, an order-status reply — or an empty canvas with the step tray open on Triggers, so your first choice is still what starts the flow. Call flows offer their own recipes and open with the voice trigger ready.
- Passwords and keys are never stored. If a step calls another system using a secret in its headers, the record keeps the header name but never its value.