Skip to content

Introduction

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 on the Activity page. The Run captures who triggered the work, when it started and finished, what configuration it used, what it produced, and what its current status is.

For per-operation walkthroughs with screenshots and per-block tables, see the By Operation Type section on the Runs overview.

What a Run is for

A Run is the unit of execution and audit in Qualytics. It serves three purposes:

  1. Execution. When a user (or a schedule, or an API caller) launches an operation, a Run is created to track that specific execution. The Run holds the configuration the operation will use and the worker assignment.
  2. Observation. While the operation is in progress, the Run exposes live counters (containers processed, anomalies identified, records scanned) and a progress bar. Once finished, it stores the summary metrics, the result payload, and a downloadable log.
  3. Audit and replay. Every Run is permanent until explicitly deleted. The Activity tab shows the full history, and any Run can be re-launched via Rerun (a fresh execution with the same configuration) or Resume (continue from where the original stopped, when applicable).

A Run never mutates after it ends. To "redo" a Run with the same settings, the platform creates a new Run; the original record is preserved as part of the audit trail.

Anatomy of a Run state

Every state a Run can be in exposes the same set of visual and functional components. Understanding these components first makes the rest of the Deep Dive easier to read.

Component What it carries Varies by state?
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.
State icon An MDI glyph that visually anchors the state. Yes. One icon per state.
Progress bar Containers processed against total requested (for example, 4 / 14 Tables). Yes. Hidden when Queued; live while Running; frozen on terminal states.
Action buttons The set of operations the user can perform on this Run: Abort, Resume, Rerun, Delete. Yes. Driven by state and operation type. See Available Actions.
Warning indicator A small icon next to the Run ID when the worker produced log entries during the Run. Only on Success runs that produced logs (the badge stays Success).
Summary metrics Counters specific to the operation: anomalies identified, records scanned, checks added, containers profiled, etc. Live while Running; frozen on terminal states. Partial when Aborted/Failure.
Triggered By / Aborted By The user, schedule, or system that initiated (or stopped) the Run. The label changes to Aborted By on Aborted runs.
Logs An inline block in the row summary plus a wider block on the operation detail page. Active states stream lines live; terminal states freeze the log.

States at a glance

The five canonical states plus the Warning indicator are described below in brief. For the detailed walkthrough of each, see the By Operation Type section on the Runs overview.

Icon State Typical action available What it means
Queued Abort The Run is registered but no worker has picked it up yet.
Running Abort A worker is actively processing the Run; counters update live.
Success Rerun, Delete The Run finished cleanly. Summary metrics and result payload are authoritative.
Success + Warning indicator Rerun, Delete A Success Run that recorded log entries during execution. Status stays Success; the warning icon only appears next to the Run ID to flag that the log is worth opening.
Failure Resume (when supported), Rerun, Delete The Run stopped because of an unrecoverable error. Partial results are preserved; the operation log carries the root cause.
Aborted Resume (when supported), Rerun, Delete A user (or the system) stopped the Run before completion. Partial results are preserved.

The Run row badge is text-only. The glyphs above appear on the operation detail page as the timeline step icon; on the Activity list, the only icon next to a Run ID is the warning indicator (when a Success Run produced logs). Queued and Running are shown in the UI as an animated spinner; the static loader icon in the table above represents both states.

Next: