Run Overview

The Overview tab of a Run's detail page shows everything the platform recorded about that execution, with the exact settings the operation ran with, its result metrics, the log output, and a chronological timeline of what happened. Where the row on the Activity tab is built for following many Runs at once, the detail page is built for inspecting one, and it keeps its own URL, so you can bookmark a Run or share it with a teammate.

The page's other tab, Results, covered on Run Results, breaks the outcome down per table or file, and only appears for the operation types that produce that breakdown (Scan, External Scan, Profile, and Promote).

While the Run is active, the page updates itself, so the progress, metrics, and timeline entries below reflect the execution live without refreshing the browser.

How to reach it

On the Activity tab, click the View operation button next to the Run's ID and type. The page opens on the Overview tab.
On an expanded Run row, the Results button (shown for Scan, External Scan, Profile, and Promote) opens the same page directly on the Results tab.
On an anomaly's side panel, the link to the scan that identified it lands on the Overview tab of that Run.
On a Flow execution, the View operation button on a node opens the Run that node triggered.

Operation

The first section repeats the Run's key details, the same information the Activity row summarizes, laid out as labeled fields:

Field	Example	Description
Status	`Success`	The Run's current state, as a colored badge. The palette and meaning of each state are on the Run States table.
Started At	`Sep 7 2026, 2:32 PM (UTC)`	When the Run started, in your local time zone.
Duration	`Took 2 minutes`	How long the Run took. While the Run is active it reads `Queued for...` or `Running for...` and keeps counting; once the Run ends, it freezes at the total.
Progress	`8 / 14 Tables`	Scan, External Scan, and Profile only. A progress bar with the count of containers processed successfully against the total requested.
Triggered By	`Jane Doe`	Who or what started the Run, showing the user's avatar and name, `System`, or the trigger source. On an Aborted Run, the field becomes Aborted By and names who stopped it, with the original trigger kept in the tooltip.
Schedule	`Nightly scan`	The named schedule behind a recurring Run, or `No schedule` for a Run started on demand. When a Flow triggered the Run, the field is labeled Flow and names it.
Remediation Strategy	`None`	Scan and External Scan only. The remediation strategy the scan ran with.

Settings

The Settings section is the read-only snapshot of the configuration the operation executed with, mirroring the fields of the operation's own form. The set of fields follows the operation type (an External Scan shows the Scan set); Promote Runs carry no configurable settings, so the section does not appear for them.

ScanProfileSyncExportMaterialize

Field	Example	Description
Check Categories	`All`	Which check categories the scan applied (Metadata, Data Integrity, or All).
Incremental	`Enabled`	Whether the scan used the Incremental read strategy or read everything (Full).
Read Record Limit	`All`	The maximum number of records read per partition, or `All` when no limit was set.
Archive Duplicate Anomalies	`Disabled`	Whether anomalies duplicating an existing open anomaly were archived instead of listed as new.
Reactivate Recurring Anomalies	`Disabled`	Whether previously resolved anomalies that flagged again were reopened.
Auto-Resolve Anomalies	`Enabled`	Whether open anomalies that no longer flagged were resolved automatically.
Max Record Anomalies per Check	`100`	The rollup threshold above which a check's record anomalies collapse into a single shape anomaly.
Max Source Examples per Anomaly	`10`	How many source records were kept as examples for each anomaly.

Field	Example	Description
AI Effort	`High`	The AI Effort level the profile ran with.
AI Managed Checks	`Draft`	Whether the AI-managed checks the profile produced were created in Draft or Activated automatically. Hidden when AI Effort is Off.
Read Record Limit	`All`	The maximum number of records read per partition, or `All` when no limit was set.
Greater Than Time	`Sep 1 2026, 12:00 AM (UTC)`	The starting timestamp of an incremental profile. Shown only when one was set.
Greater Than Batch	`1024`	The starting batch value of an incremental profile. Shown only when one was set.

Field	Example	Description
Prune	`Enabled`	Whether the sync removed containers that no longer exist in the source.
Recreate	`Disabled`	Whether the sync restored containers previously removed in Qualytics that still exist in the source.
Include	`Table, View`	The container types the sync included. Shown only when the sync was limited to specific types.

Field	Example	Description
Asset Type	`Anomalies`	What the export wrote to the Enrichment Destination (Anomalies, Quality Checks, or Field Profiles).
Reveal Masked Values	`No`	Whether masked values were written in clear text.

Field	Example	Description
Record Limit	`All`	The maximum number of records written per partition, or `All` when no limit was set.
Reveal Masked Values	`No`	Whether masked values were written in clear text.

Summary

The Summary section holds the Run's key result metrics as stat cards. It appears for the operation types that report them (Scan and External Scan, which share the same set, plus Profile and Promote) and updates live while the Run is Running. On a file-based datastore, the labels below name file patterns instead of tables.

ScanProfilePromote

Field	Example	Description
Tables Requested	`14`	How many containers the scan targeted.
Tables Scanned	`12 / 14`	How many containers finished successfully. The total appears alongside only while some containers remain unprocessed or failed.
Partitions Scanned	`56`	How many partitions were processed across all containers.
Records Scanned	`1,203,441`	How many records were read and checked.
Anomalies Identified	`32`	How many anomalies the scan produced, with Open and Archived counters alongside.
Anomalies Auto-Resolved	`4`	How many previously open anomalies the scan resolved automatically. Shown only when Auto-Resolve Anomalies was enabled.

Field	Example	Description
Tables Requested	`14`	How many containers the profile targeted.
Tables Profiled	`12 / 14`	How many containers finished successfully. The total appears alongside only while some containers remain unprocessed or failed.
Records Processed	`1,203,441`	How many records were read.
AI Checks Synced	`27`	How many AI-managed checks the profile synchronized, with Added and Updated counters alongside.

Field	Example	Description
Destination Datastore	`Analytics DW`	The datastore the promotion wrote to.
Destination Container	`CUSTOMERS`	The container the promotion wrote to. Shown only when the promotion targeted one.
Quality Checks Requested	`20`	How many entities the promotion carried. The label follows what was promoted (quality checks, computed fields, or computed tables and files).
Quality Checks Promoted	`18 / 20`	How many entities landed in the destination, with Created, Updated, Skipped, and Failed counters alongside.

Logs

The Logs section appears only when the Run recorded log output. On a Run that finished successfully, it shows a warning card, marked with an amber icon, stating the operation reported a warning; on a Failure, it shows an error card, marked with a icon, leading with what went wrong. In both cases, clicking the card's Details toggle reveals the raw log output.

The output is plain text, one line per event, in the order the events were recorded, and a copy button on the block copies it whole. It arrives with the Run's final result and does not change afterwards: on a Scan or Profile it gathers the run-level outcome plus the message of each container that failed or was aborted (successful containers add no lines), and on the other operation types it carries the message the operation ended with. Expect the non-fatal issues recorded during execution here (such as a container error that did not stop the operation, or a warning the source datastore raised) and, on a Failure, the root cause of the stop. On a successful Run, this same recorded output is what places the Warning indicator next to the Run ID, so reviewing it tells you whether the warning matters before relying on the result.

Timeline

The Timeline section lists the Run's events chronologically, newest at the top, so reading it bottom-up replays the execution:

Entry	Example	Description
Operation Started	`Triggered by Jane Doe`	Always the bottom entry, with a icon, the start timestamp, and who or what triggered the Run.
Container entry	`CUSTOMERS`	Scan, External Scan, and Profile only. One entry per container processed, named after it, with the icon and color of that container's own result and its counters underneath (a Scan shows records processed, duration, and anomalies identified; a Profile shows records processed, fields profiled, and AI checks synced).
Operation In Progress	`Running...`	A spinning entry shown while the Run is Queued or Running, with the elapsed time.
Operation Success / Failure / Aborted	`Operation Success`	The top entry once the Run ends, with the icon and color of the outcome (green for Success, for Failure, for Aborted), the total duration, and, on an Aborted Run, who aborted it.