The Runs page
Every run in the project lands on Runs — scripts, flows, AI Scraper robots and e-mails, whether a person, a schedule, an API call or an event started them. The list is filtered, searched and counted on the server, so the figures in the side panel always describe exactly the rows you are looking at. This guide covers the filters, the search language, the flow tree and the drawer that opens on a click.
- Narrow the list by period, kind, status and Waiting for you
- Search by words and by input conditions such as amount>100
- Unfold a flow run into the runs it started
- Read a run in the drawer and run it again with the same inputs
What the list shows
One row per top-level run, newest first. A script that a flow ran is not a row of its own — it sits under its flow (see the tree below), so one flow run counts as one run, not one plus its steps. Each row shows the language or kind, the item’s name and path, and four labelled columns: Triggered by, Duration, Ran at (the exact moment, with seconds; today shows only the time) and Status.
| Triggered by | Shows |
|---|---|
| A person | Their e-mail; hover or click for a card with name and e-mail |
| API | The name of the token used (or Public endpoint) |
| Schedule | The schedule’s name |
| Flow | The parent flow (for a flow started by a subflow step) |
| E-mail · Database change · MQTT | The event trigger’s name |
The list loads more by itself as you scroll down; Back to top appears once you are far down, and the filter bar stays pinned at the top. Live keeps it updating as runs start and end.
Filter the list
- Pick a period
Today, 7 days (the default), 30 days, All time, or Custom range with From and To. A run belongs to the period it was queued in — the one moment every run has, finished or not.
- Kind and status
Kind: All, Script, Flow, AI Scraper, Email. Status: All, Running, Queued, Success, Failed, Completed with errors, Waiting for approval, Rejected.
- Waiting for you
Waiting for you keeps only the flow runs stopped at an Approval step that you can decide, each with Review.
- Search
Type in Search name or value · key:value · OR. Matching words and conditions are highlighted in the rows (next section).
The search language
A plain word matches the item’s name and any value in the run’s inputs or output — a customer id you passed, an e-mail address a script returned. A key followed by an operator is a condition on one input; dotted keys reach inside objects (customer.tier=gold). Case and accents are ignored.
| You type | Matches runs where |
|---|---|
invoice | the name, an input value or an output value contains “invoice” |
"late fee" | the exact phrase, spaces included |
customer:acme | the input customer contains “acme” |
month=2026-09 · status!=draft | the input equals / does not equal the value (an absent input counts as “not equal”) |
amount>100 · < · >= · <= | the input is a number in that range |
a b · a AND b · a OR b · ( … ) | both / either; AND binds tighter than OR; && and || work too |
# failed imports for one customer, in September
import customer:acme month=2026-09
# big orders, from either region
amount>=1000 (region=south OR region=north)Flow runs as trees
A flow row has a caret: Show the runs it started. Under it, indented, come the executions — each script step that ran and each subflow it started — in the same layout as a top-level row. A step that ran inside a loop carries #2, #3… (Loop iteration 2). Conditions, loop headers and steps that never ran are the flow’s own wiring and do not appear; the flow’s canvas shows them. Children have no Triggered by column — the nesting already says it.
Clicking a child opens its parent flow run focused on that step — and on that loop iteration — so you see the step in context.
The run drawer
Click a row and a drawer slides in from the right; the page stays usable, and clicking another row swaps it. Drag its edge to resize it (the width is remembered); click outside or press Esc to close.
| Run | Tabs |
|---|---|
| Script | Output (parameters, result, the received request for API runs) · Logs · Code (the exact code that ran) |
| Flow | Data (inputs, output, the run drawn on a read-only canvas) · Steps · Logs grouped by step · Timeline |
- Values show as a table or JSON (Table view / JSON view); Maximize gives one section the whole drawer.
- Open in editor / Open on flow page opens the item in a new browser tab.
- Run again starts the same item with the same inputs (… started again with the same inputs).
- A row’s right-click menu has Open details, Open in new tab and Copy link.
The Statistics panel
On the right, Statistics describes the filtered list: Total runs, running now, success rate and average duration, the Run trend per day, By status, Most run and Recent failures. By status is the one figure that ignores the status filter — it is also how you pick one: click a status to filter by it. On the same page, Scheduled · next 24 h shows what is about to run, late firings and any that Didn’t start with the reason.
Good to know
- A step’s name is not searchable from the top level: search the flow, then unfold it.
- A run whose item was deleted stays, marked deleted target — the record remains, but there is nothing to open.
- Your access decides what you see: with no access to an area (scripts, flows, runs), its runs are not listed.