Anatomy of a Run
Every state a Run can be in is presented through the same set of visual and functional components, on the Activity list row and on the operation's detail page (Run Overview and Run Results). This page names each component and describes how it changes as the Run advances; understanding them first makes the rest of the Deep Dive easier to read.
Run Row
Every Run appears as a row on the Activity list. These components are visible without expanding it:
| Component | What it shows | Varies by state? |
|---|---|---|
| Operation ID and type | The Run's unique identifier (for example, #53201) and its operation type. The icon next to the ID opens the operation's detail page. |
No. Fixed for the life of the Run. |
| Status badge | A colored pill with the state label (Queued, Running, Success, Failure, Aborted) on the Run row and the operation detail page. |
Yes. Color and label change per state. |
| Time info | Started At with the exact start timestamp, and Duration with the elapsed time. | Yes. Duration ticks up live on active states and freezes at the total once the Run ends. |
| Progress bar | A counter above the bar with containers processed against the total requested (for example, 4 / 14 Tables), the bar itself, and a status line under it carrying the phase message or the operation verb (see Phase messages below). |
Yes. Hidden when Queued; live while Running; frozen on terminal states. Export and Materialize show only the requested total, with the bar animating without a fraction while active, and Sync shows no counter at all. |
| Triggered By / Aborted By | The user, schedule, API call, or Flow action that started the Run. | Yes. The label changes to Aborted By on Aborted runs. |
| Schedule | The named schedule when the Run is recurring, otherwise No schedule. |
No. Fixed for the life of the Run. |
| Quick stats icons | A cluster of small icons on the right of the row summarizing the run's configuration and results at a glance, each with a tooltip. The set depends on the operation type; see Quick Stats Icons for the breakdown per operation. | Yes. Result counters, such as anomalies identified, update live while Running. |
| Warning indicator | A small icon next to the Run ID when the Run recorded log entries during execution. | Only on Success runs that produced logs (the badge stays Success). |
Expanded Row and Detail Page
Clicking the row expands it in place, and the icon next to the ID opens the operation's detail page, covered in depth on Run Overview and Run Results. These components appear there:
| Component | What it shows | Varies by state? |
|---|---|---|
| Settings | The read-only configuration the Run executed with, on the expanded row. The set of fields mirrors the operation type (a Scan shows check categories, record limits, anomaly options, and the remediation strategy). | No. Fixed for the life of the Run. |
| Action buttons | The actions available for the Run (Abort, Resume, Rerun, Delete), plus Results, on the expanded row. | Yes. Driven by state and operation type. See Available Actions. |
| Summary metrics | Counters specific to the operation type (anomalies identified, records scanned, checks added, containers profiled), on the expanded row and the detail page. | Yes. Live while Running; frozen on terminal states. Partial when Aborted/Failure. |
| Logs | An inline block in the row summary plus a wider block on the operation detail page. | Yes. The Run-level log appears with the final result; container-level logs surface earlier, as each container finishes. |
| State icon | The glyph that anchors the state on the operation detail page's timeline (on the list, the badge is text-only). | Yes. One icon per state; see Run States. |
Phase messages
While a Scan or Profile is Running, the status line under the progress bar on the operations list names the phase the run is currently in, so you can tell whether the time is going into reading from the source or into processing the data:
| Phase message | What it means |
|---|---|
Loading source data… |
The operation is reading records from the source datastore. |
Analyzing data… |
The records have been read and the platform is processing them. |
The line follows the current phase and updates as the run moves between them. The other operation types do not report phases; while they are Running, the status line keeps the operation verb instead (for example, Syncing... or Exporting...). Once any Run reaches a terminal state, the line shows the outcome, either the past-tense verb (Scanned, Profiled, Synced, and so on) or Aborted.
See also
-
How It Works
What a Run is for, what does not appear as a Run, and the contexts of the Activity tab.
-
Details
The Overview tab of the detail page, with the Run's key details, settings, summary metrics, logs, and timeline.
-
Results
The Results tab of the detail page, with the per-container breakdown of a Scan, Profile, or Promote.
-
Quick Stats Icons
The icon cluster on the right of the Run row, broken down per operation type.
-
States
The five canonical states plus the Warning indicator, and what each one means.
-
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
The user roles and team permissions behind viewing Runs and acting on them.