Executions
Each time a flow runs, AI Studio records an execution, also called a run. It keeps the run's status, the version of the flow that ran, and what every step received and returned, so you can check that a flow did what you expected and find out why it didn't.
You can see runs in two places:
| Where | What it shows |
|---|---|
| Executions in the sidebar | Runs of every flow in the workspace, with filters. |
| Run history in the flow editor | The Recent Runs of the flow you're editing. Click View all executions to open the full list. |
The Executions list
Each row is one run, newest first:
| Column | Shows |
|---|---|
| Status | Where the run is now. See Execution statuses. |
| Flow | The flow that ran. |
| Run ID | The run's ID, with a button to copy it. |
| Trigger | What started the run: Manual, Webhook, Schedule, Event or Sub-flow. |
| Version | Published: Version n for a run of a published version, or Unpublished for a test run from the editor. |
| Started, Duration | When the run started and how long it took. |
The list keeps up while the page is open. When new runs arrive, a new runs button appears above the list. Click it to jump to the top and show them.
A run that called other flows with Call Sub Flow can be expanded to show the sub-flow runs under it.
Filtering
| Filter | Use it to |
|---|---|
| Run ID | Jump to one run. Paste the full 24-character ID, for example the subFlowRunId from a Call Sub Flow step. |
| Flows | Show runs of some flows only. |
| Status | Show only, say, Failed and Timed out runs. |
| Trigger | Show only runs started a certain way. |
| Date range | Narrow the time window. |
| All / Published / Test | Show every run, only runs of a published version, or only test runs from the editor. |
Execution statuses
| Status | Meaning |
|---|---|
| Queued | The run is waiting to start. |
| Running | Steps are running now. |
| Waiting | The run is paused at a Wait step, for a time or for someone to respond. It continues when the wait ends. |
| Completed | Every step that should run finished. |
| Failed | A step failed and its Error Handling was Stop flow. |
| Timed out | The run went on too long, or stopped making progress, and AI Studio ended it. See Limits. |
| Terminated | Someone stopped the run with Terminate Run. |
| Cancelled | The run was cancelled before it finished, for example because its flow was deleted while the run was queued or waiting. |
To stop a run that is still going, open it and click Terminate Run, then confirm with Terminate. This can't be undone.
Node results
Click a run to open it. The page shows the flow as it was when that run started, with the Run nodes listed beside it. Select a step to see four tabs:
| Tab | Shows |
|---|---|
| Input | The settings the step ran with, after references to earlier steps were filled in. |
| Output | What the step returned. Later steps used this data. |
| Logs | Messages the step wrote while it ran. |
| Error | Why the step failed, if it did. |
A few things to know when reading a run:
- This step did not run means the run never reached the step, for example because it was on a branch that wasn't taken, or an earlier step stopped the run.
- For a Loop, choose an iteration to see what each step did on that pass.
- A Call Sub Flow step lists its Sub-flow runs. Open one to see the sub-flow's own steps.
- If you've changed the flow since the run, a banner says so. The graph still shows the flow as it ran. Use Open flow in editor to go to the current version.
How long executions are kept
The Executions list shows runs from the last 14 days. Older runs don't appear in the list or its filters.