Run Results
The Results tab of a Run's detail page breaks the outcome down entity by entity, so you can see how each table, file, or promoted item fared rather than just the Run-level totals. It is where you go from "the scan found 32 anomalies" to which containers produced them, which checks failed, and which records were flagged.
The tab exists only for the operation types that produce this breakdown, which are Scan, External Scan, Profile, and Promote. Sync has no per-entity results. Export and Materialize show a View Results button on the expanded Run row instead, which opens the destination where the records were written.
While the Run is Running, the lists below update themselves, so counts and per-container statuses reflect the execution live.
How to reach it
- On an expanded Run row on the Activity tab, click the Results button.
- On the Run's detail page, switch from the Overview tab (covered on Run Overview) to the Results tab.
- On an expanded Scan, External Scan, or Profile row, the information icon next to the Summary heading carries a tooltip offering to open the Results page for the full breakdown.
Scan Results
For a Scan or External Scan, the tab lists one card per container the operation targeted. A filter bar at the top offers a search by container name, sorting by anomalies, checks, or name, filters by container type and tag, a switch to show only containers not analyzed, and pagination for long lists.
Each card summarizes how that container's scan went:
| Component | Description |
|---|---|
| Status dot | The result of that container's own scan, independent of the Run-level state. |
| Container name and type | Identifies the container. The View button next to it opens the container's details page. |
| Passed Checks | How many quality checks ran against the container without producing anomalies. The pill is green when the count is above zero and grey at zero. |
| Failed Checks | How many quality checks produced at least one anomaly. The pill is tinted when the count is above zero and grey at zero. |
| Anomalies Identified | How many anomalies the container produced, with Open and Archived counts in the tooltip. Clicking the pill opens the container's anomalies. When the container scanned successfully with no anomalies, a green shows instead; on a container whose scan failed, the same spot shows a grey alert rather than the green check. |
| Anomalies Auto-Resolved | How many previously open anomalies the scan resolved automatically on that container. Shown only when Auto-Resolve Anomalies was enabled; clicking it opens the auto-resolved list. |
| Expand toggle | Opens the container's per-scan details, described below. |
Per-container details
Expanding a card reveals sub-tabs with the container's own breakdown:
- Partitions lists every slice of the container the scan processed. Each row carries a status dot showing whether the partition passed, completed with warnings, or failed, the partition's location (a virtual partition shows
Virtual, withMetadataas its location), the records processed, the timestamp when its result was recorded, and an anomaly count pill that opens that partition's anomalies. A search box and an All / Passed / Failed filter narrow the list. - Checks lists every quality check applied to the container, each with its ID, name, and anomaly count, with the row highlighted when the check produced anomalies. Clicking a row opens the check's side panel. The same search box and All / Passed / Failed filter apply.
- Source Records appears only when the scan captured source records, and lists the distinct source records identified as anomalous, each with the count of anomalies tied to it. A toolbar offers sorting, revealing masked values, choosing which fields to display, refreshing, and downloading the records.
Profile Results
For a Profile, the tab lists one card per container, behind the same search, filter, and pagination bar, with the sort options adjusted to Profile (fields profiled, records, checks, or name). Each card shows the container's status dot, name, and type, plus counter pills for the records processed, the fields profiled, and the AI Checks Added and AI Checks Updated on that container.
Expanding a card reveals a metrics grid (Records Processed, Fields Profiled, AI Checks Synced, AI Checks Added, and AI Checks Updated) and a Partitions sub-tab listing every partition the profile processed, along with the container's log output when it reported one.
Promote Results
For a Promote, the tab lists every entity the promotion carried, which can be quality checks, computed fields, or computed tables and files, following what was promoted. Each row shows a status dot with the entity's individual result and buttons that open the source entity and its promoted copy in the destination datastore. Filter chips at the top narrow the list by result:
| Result | Description |
|---|---|
| Created | The entity did not exist in the destination and was created there. |
| Updated | The entity already existed in the destination and was overwritten with the promoted version. |
| Skipped | The entity was left untouched in the destination; its row carries the reason, such as the definition being identical on the destination. |
| Failed | The entity could not be promoted; its row carries the reason. |
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.
-
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.
-
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.