Flow Executions

Every run of a Flow is recorded as an execution. This page is the reference for where executions are listed, the states they move through, and what the read-only execution page shows.

Editing is locked while executions run

While a Flow has executions in progress, its canvas is read-only. Abort the running executions or wait for them to finish before editing. See How a Flow Works.

The Definitions and Executions Tabs

The Flows page opens on Definitions, which lists the Flows themselves, and Executions lists their runs. Each row of the Definitions tab shows:

Column	What it shows
Name	The Flow's name, with its description behind an info control when it has one.
Trigger Type	The trigger the Flow runs on. On a Schedule trigger, a control opens the schedule and the next run.
Actions	How many actions the Flow holds.
Datastores	The datastores the Flow's trigger filters on.
Tags	The tags the trigger filters on. The column's own label follows the trigger, reading Datastore Tags, Table or File Tags, or Anomaly Tags.
Last Triggered	How long ago the Flow last ran, with the exact timestamp on hover.

To sort or narrow either tab, see Filter and Sort Flows.

Where Executions Are Listed

Executions appear in two places: the Executions tab of the Flows page lists runs across all Flows, and each Flow's page has its own Executions tab scoped to that Flow.

Each row shows the Flow, the execution identifier, a status badge, the trigger type, when it started, and how long it ran (or has been running). For event-based triggers, the row also shows the triggering object, such as the operation, table or file, or anomaly that started the run, with a shortcut to open it.

From the executions list you can also stop or clean up runs: Abort is available while an execution is running, and Delete once it has finished, both per row and in bulk. See Abort an Execution and Delete an Execution.

Execution States

Each node in an execution reports one of six states, listed in the legend at the bottom-right corner of the execution page:

State	Meaning
Success	The action completed successfully.
Failure	The action failed.
Aborted	The action was stopped by an abort.
Skipped	The action did not run, for example because an upstream action failed.
Running	The action is in progress.
Pending	The action has not started yet.

While a step is running, its node shows a dotted-line animation; when the action completes, the node changes color to reflect the final state.

The Execution Page

Clicking an execution opens its page, which shows the same graph as the Flow, rendered read-only, with each node colored by its state and updating in real time while the run is in progress. No edits can be made here.

The root node is labeled Flow Execution. Clicking it opens a panel with the run's general information (Flow and execution identifiers, start and end time, duration, status) and its logs, with a button to copy the log message.
Clicking an action node opens its Historical Configuration: the action's settings exactly as they were at the moment the Flow ran, including selected inputs, parameters, and options, even if the Flow has been edited afterward.
Actions that started an operation carry a View operation shortcut, which opens that operation's own page on its datastore, with the run's full results.