Runs
A Run is a single execution of an operation against a source datastore. Every operation that fires (manually, on a schedule, or via the API) is recorded as a Run with its own status, timing, summary metrics, and downloadable result.
Deep Dive
-
Introduction
What Runs are for, the parts a state exposes (badge, icon, action buttons, summary, logs), and the five states at a glance.
-
Lifecycle
State diagram of how a Run moves between Queued, Running, Success, Failure, and Aborted, plus where to find the per-container progress and logs.
-
Available Actions
Abort, Resume, Rerun, and Delete: when each one is shown, what it does, and which operation types support it.
-
Permissions
Team-permission matrix that governs which roles can Abort, Resume, Rerun, and Delete a Run.
By Operation Type
For end-to-end walkthroughs of what a Run looks like in each state on a specific operation type (with screenshots, per-block tables, and operation-specific quirks), see the dedicated page per state:
-
Scan
Walkthrough of what a Scan Run looks like in each state.