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. The Definitions tab shows the Flows as cards or as a list, following your view preference. Each Flow shows:

Column	What it shows
Name	The Flow's identifier and name, with its trigger icon and a green or grey dot for active or deactivated.
Flow	The trigger followed by as many actions as fit, with a count for the rest.
Conditions	The trigger's filters, each with its name and a count, or its value when it holds a single one. Hovering a condition lists its values.
Related datastores	The datastores the Flow relates to, All when it reaches every datastore, or None. See Flow Permissions.
Recent runs	The result of the last five executions, oldest first.
Last Triggered	How long ago the Flow last ran, with the exact timestamp on hover.
Created By	Who created the Flow. Flows that ship with the platform show Qualytics.

Clicking a Flow opens its side panel, with the trigger, your access (You can edit or Read only), the creator, a preview of the Flow, its related datastores, its conditions, and its recent runs. Manage flow opens the canvas (View flow when the Flow is read only for you). To users who can manage the Flow, the header also offers Execute (Execute Now on a Schedule Flow) for Flows that can be started by hand, Activate or Deactivate, and Delete.

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 execution identifier and its Flow, a status badge, the trigger type, the Conditions the trigger had when the run started, how long it ran (or has been running), and Triggered By. Editing the Flow later doesn't change the conditions shown for its past runs, as long as the Flow had saved history when they ran. A run older than the Flow's history, such as an early run of a Flow that ships with the platform, shows the Flow's current settings instead. Triggered By shows the triggering object of an event run, such as the operation, table or file, or anomaly that started it, with a shortcut to open it. Otherwise it shows the user who started the run, or Qualytics for a scheduled run.

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). When the run recorded a log message, a Logs section also appears, with a copy button that shows when you hover over the message once the run has finished.
Clicking the trigger node opens its settings read-only, with the trigger type, schedule, and filters the run started with. A run older than the Flow's history shows the current settings.
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.