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 are gated by the Editor team permission on the target datastore. See Permissions for the full matrix.
Support matrix
| Icon | Action | When it is shown | Supported by | What it does |
|---|---|---|---|---|
| Abort | While the Run is Queued or Running | All operation types | Signals the worker 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, 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. | |
| Rerun | After the Run ends in any terminal state | Sync, Profile, Scan, 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. | |
| Delete | After the Run reaches a terminal state | All operation types | Removes the Run record and its summary metrics from the Activity list. Anomalies, computed data, and other downstream artifacts produced by the Run are not removed; only the Run's own record is. |
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, Materialize). External Scan supports neither Resume nor Rerun because it only records results from outside Qualytics; there is nothing to continue or re-execute from the platform.
For the team-permission requirements that gate each of these actions, see Permissions.