Runs Available Actions¶
Each Run exposes a set of action buttons that depend on (1) the Run's current state and (2) the type of operation. All actions require the Editor team permission on the target datastore (users with the Admin role bypass team permissions). Global Export runs are the exception: they are gated by role, as described on Permissions. Delete also requires that you started the Run, unless you have the Admin role. See Permissions for the full matrix.
Support matrix¶
| Action | When it is shown | Supported by | What it does |
|---|---|---|---|
Abort |
While the Run is Queued or Running | All operation types | Signals the platform to stop the Run as soon as possible. Partial results captured up to the stop point are preserved. The Run lands on Aborted. Aborted By shows the user, or System when the platform stopped the Run automatically. |
Resume |
After the Run ends in Aborted or Failure | Profile, Scan, Promote (not Sync, External Scan, Export, Global Export, Materialize) | Continues the same Run from where it stopped. Only containers (or partitions) that had not finished are processed. Containers already completed in the original Run are not re-read. A Run that targeted no container is refused, since there is nothing to resume. |
Rerun |
After the Run ends in any terminal state | Sync, Profile, Scan, Export, Global Export, Materialize, Promote (not External Scan) | Starts a brand-new Run with the same configuration as the original. Every container is processed from scratch, regardless of whether it succeeded before. A Scan that picked specific checks asserts the same picks again, and a Scan whose tables were chosen by tag resolves the tags again. |
Delete |
After the Run reaches a terminal state | All operation types | Removes the Run record and its summary metrics from the Activity list. Deleting a Scan or External Scan also permanently deletes the anomalies it found, recalculates quality scores, and makes the previous successful scan the latest one when the deleted Run was the latest. Deleting a Profile removes its profile results and, when it was the latest profile, makes the previous successful profile the latest one. Data written by Sync, Export, Materialize, and Promote stays in place. |
When to use each action¶
- Abort is the only way to stop an active Run. There is no destructive side effect: anomalies, container metadata, and partial counters already written are kept.
- Resume avoids reprocessing data the system has already validated. Use it when you want to pick up exactly where the original Run stopped. The button's tooltip names the unit of work it will pick up.
- Rerun is the right choice when upstream data has changed, when the configuration needs to be re-validated end to end, or when Resume is not available for the operation type.
- Resume is unsupported for operations that cannot pick up from the last completed unit of work (Sync, Export, Global Export, Materialize). External Scan supports neither Resume nor Rerun. To scan the data again, start a new External Scan.
For the team-permission requirements that gate each of these actions, see Permissions.
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, and where a Sync, Export, or Materialize wrote its results.
-
Anatomy
The components every Run exposes, from the status badge to the progress bar with its phase messages.
-
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.
-
Permissions
The user roles and team permissions behind viewing Runs and acting on them.