Tutorial · Runs
Runs: track every execution in flight
The Runs screen is your operations control tower. See every live execution, what is overdue, who owns it, and when it is due, then drill in to act.
6 min read · Managers & operators
The Runs screen
Every execution, one table
Open Runs from the sidebar. The status row across the top counts what is In progress, Overdue, and Completed, plus a Stalled filter for runs with no recent activity. Below, every run is a row: priority, name, its Flow, live status, due date, owner, and start date. Sort any column, or switch to the Calendar view to see runs by date.
Reading the status row
The counts at the top are also filters. Click one to narrow the table to just those runs.
In progress
Actively running
- •Started and not yet finished
- •Tasks are moving through the flow
- •Your normal working set
Overdue
Past due date
- •Blew the run or task deadline
- •Where escalations kick in
- •Triage these first
Stalled
No recent activity
- •Running but untouched for N days
- •Often a hidden blocker
- •The 7d window is adjustable
Walkthrough
Find and act on the right run
- 1
Narrow with filters
Use the Flow, Status, and Owner dropdowns, or the search box, to cut a long list down to what you care about, for example every Overdue run owned by one person.
- 2
Sort by what matters
Click a column header (Due date, Started, Priority) to sort. Combine with the Overdue filter to put the most urgent work on top.
- 3
Tune your columns
The Columns button lets you show or hide fields so the table matches how your team triages. Priority badges (P1, P2) surface the most important runs at a glance.
- 4
Open a run to act
Click any row to open the run detail, where you complete tasks, view the audit trail, and see progress. That screen is covered in the Block C tutorials.
- 5
Export or schedule
Export the current view to CSV for reporting, or use Start run to launch a new execution without leaving the screen.
Make Overdue plus sort-by-due-date your morning triage view. It answers what is on fire in one glance, and pairs perfectly with the Daily Ops Review flow.
Common questions
What makes a run count as Overdue?
A run is overdue when it passes the deadline set by the Flow's SLA or due-date rules, or when a task inside it is past its own deadline. Overdue runs are where escalation notifications trigger.
What is the difference between Overdue and Stalled?
Overdue is about the clock: a deadline passed. Stalled is about activity: nobody has touched the run in a set window (7 days by default), even if it is not technically late yet. A run can be one, both, or neither.
Can I see runs on a calendar?
Yes. Toggle List / Calendar at the top right to place runs on their due dates, which is useful for spotting clustering and planning capacity.
Turn run chaos into a control tower
See how teams triage hundreds of live runs without a spreadsheet, on a guided demo.