Runs
Enterprise module
Flows is part of the Enterprise edition. See Flows.
Every execution of a flow is a run. Open Operate → Agent Observability → Flow runs to see the runs of every flow in the project: tests, agent calls, API calls and sub-flows.
The runs list
The list shows the Flow, the Agent, the Trigger, the Status, when it Started, its Duration and the number of Steps. Summary tiles above it show Runs (24h), Success rate, Avg duration and Waiting approvals. Filter by Status, Trigger and Period, or search by flow name. View run opens the run, and Open flow opens the flow.
Statuses: Queued, Running, Waiting, Succeeded, Failed, Canceled.
Trigger values are Manual, Test, API, Agent tool, Agent conversation, Subflow and Import (runs brought in with a Studio import). A run you started from the test panel shows Test.
Run detail
A run has four tabs:
| Tab | Shows |
|---|---|
| Steps | The timeline of steps with status, attempt and loop iteration. Select a step to see its Input, Output, Error, Logs and token use. A value larger than the inline limit (256 KB) is marked Truncated. |
| Input / Output | What the run received and what it returned. |
| Events | The ordered event log: run.queued, run.started, step.started, step.succeeded, step.failed, step.retrying, run.waiting, approval.requested, approval.decided, run.succeeded and so on. |
| Messages | The conversation messages a Conversation flow emitted. |
The header gives the flow and version (Draft or v3), the trigger, Run as (the user or token that started it), the agent and session, the parent run for sub-flows, timings, Active time, tokens, cost, and for a failed run the Failure reason: A step failed, Interrupted while a step was running, The run timed out, The run lost its permission, Invalid input or definition, A run limit was exceeded, The run state grew too large or Internal error.
Step input and output are run details: a reader with read access only sees the run summary.
Waits
A run that cannot go on yet is Waiting. The wait is stored with the run, not held in memory, so it survives a restart and uses no resources. The kinds are:
| Wait | Ends when |
|---|---|
| Delay | The time passes (or you choose Skip wait). |
| Approval | A person decides, or the time to decide runs out. |
| User input / form | The person answers (in a chat) or you Submit the resume payload. A wait that times out fails the run with The run timed out. |
| Subflow | The child run finishes. |
| Agent | The agent of an AI Agent step stops asking: the person answers its tool approval or question. |
A background sweeper looks at waiting runs every 15 seconds. It wakes delays that are due, applies approval time-outs, and fails or re-dispatches runs whose worker was lost.
Cancel, resume and approve
- Cancel run stops a queued, running or waiting run. Steps already completed are kept.
- Resume continues a run that waits for a delay, an input or a form. For input and form waits you send a JSON payload.
- Approve and Reject (with an optional comment) decide an approval. Only a listed approver may decide; with no approvers listed, anyone with Flows admin access. If the step requires a distinct approver, the person who started the run cannot approve it.
All three are also in the Flows API.
Approvals
An approval is bound to the step's input when it is requested. If the step's settings change before the decision, the step fails with approval_stale and the decision is not applied. A decision is recorded in the audit log as flows.approval.decide.
Limits and environment
Per flow, the editor sets the run timeout, Max steps (default 2,000; at most 20,000) and Max loop iterations (default 1,000; at most 10,000). A flow has at most 500 steps and 1,500 connections; the run timeout is 15 minutes by default and at most 24 hours of active time. A step times out after 60 seconds by default (at most 15 minutes).
Operators set these environment variables:
| Variable | Default | What it does |
|---|---|---|
FLOWS_MAX_CONCURRENT_RUNS | 8 | How many flow runs one process executes at the same time. Runs over the cap wait in a queue. A waiting run does not hold a slot. |
FLOW_SANDBOX_MAX_PER_RUN | 8 | How many live sandboxes one run may own. Parallel branches and loops multiply them. |
FLOW_SANDBOX_READY_TIMEOUT_MS | 90000 | How long a sandbox step waits for a new sandbox to be ready. |
A project can also be limited by a service quota or, on hosted plans, a monthly flow-run allowance. A run started over the allowance is refused.
License
Starting a run, resuming one and the sweeper all need an active Enterprise license. After a license lapses, waiting runs stay as they are until it is renewed, and you can still read every run.