# Run Results

Source: https://userguide.qualytics.io/operations/runs/deep-dive/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.

Scan, External Scan, Profile, and Promote produce this breakdown. Sync, Export, and Materialize write containers instead, so their **Results** tab leads to the listing that holds what they wrote. See [Sync, Export, and Materialize Results](https://userguide.qualytics.io/operations/runs/deep-dive/results/#sync-export-and-materialize-results).

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 a Sync, Export, or Materialize row the button reads **View Results** and leads to the same place as the tab.
- On the Run's detail page, switch from the **Overview** tab (covered on [Run Overview](https://userguide.qualytics.io/operations/runs/deep-dive/details/)) 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: **Success**, **Success with warnings**, **Analysis completed; output failed**, **Failed**, or **Aborted**. **Analysis completed; output failed** means the checks ran but the container's output could not be written to the enrichment datastore, and the expanded card explains it. See [When the Output Could Not Be Written](https://userguide.qualytics.io/operations/scan/deep-dive/scan-outcomes/#when-the-output-could-not-be-written). |
| **Container name and type** | Identifies the container. The **View**  button next to it opens the container's details page. Right-clicking the card offers to copy the name, ID, or link, see [Right-click actions](https://userguide.qualytics.io/operations/runs/deep-dive/results/#right-click-actions). |
| **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 Yes shows instead. On a container whose scan failed before its checks ran, 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`, with `Metadata` as 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 (**Success**, **Success with warnings**, **Failed**, or **Aborted**), 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. |

## Right-click actions

Right-clicking a row on the Results tab of a Scan, External Scan, Profile, or Promote opens a menu that copies the row's name, ID, or links to the clipboard, so you can share a container or a promoted entity without expanding the row or opening it. The options depend on the Run type. See [Run Results](https://userguide.qualytics.io/source-datastore/tips-and-tricks/right-click-options/#where-it-works) on the Right Click Options page.

## Sync, Export, and Materialize Results

These three operations produce containers rather than a per-entity breakdown, so their **Results** tab, and the **View Results** button on the expanded Run row, open the listing that holds what they wrote:

| Operation | Where Results leads |
| --- | --- |
| **Sync** | The synced datastore's Containers listing, with the tables or files the Sync discovered. |
| **Export** | The enrichment datastore's Containers listing, narrowed to the tables that Export Run wrote. |
| **Materialize** | The enrichment datastore's Containers listing, narrowed to the materialized copies written by the Run's source datastore. |

For an Export or Materialize, the listing opens sorted by **Last Write**, newest first, and a banner at the top names what it is narrowed to: `Showing what operation #<id> wrote.` for an Export, or `Showing what <source datastore> wrote.` for a Materialize. A table appears there once it is registered in the destination, which normally follows the write within moments. Click **Show all** on the banner to drop that narrowing and list every export or materialized copy in the enrichment datastore.

A Materialize narrows to its source datastore rather than to the Run itself because each Materialize Run takes over the tables the previous one wrote, so an earlier Run would otherwise show nothing.

An Export or Materialize Run whose datastore has no enrichment datastore linked has no **Results** tab, because there is nowhere to send you. A failed or aborted Export that wrote no tables has no **Results** tab and no **View Results** button either; if you open its Results page from a link, it says "This operation did not write anything to its destination." A failed or aborted Export that wrote some tables, and a failed or aborted Materialize, still show their results. From the listing, the browser's Back button returns to the page you came from.

## See also

- **How It Works**

  What a Run is for, what does not appear as a Run, and the contexts of the Activity tab.

  [How It Works](https://userguide.qualytics.io/operations/runs/deep-dive/how-it-works/)
- **Details**

  The Overview tab of the detail page, with the Run's key details, settings, summary metrics, logs, and timeline.

  [Details](https://userguide.qualytics.io/operations/runs/deep-dive/details/)
- **Anatomy**

  The components every Run exposes, from the status badge to the progress bar with its phase messages.

  [Anatomy](https://userguide.qualytics.io/operations/runs/deep-dive/anatomy/)
- **Quick Stats Icons**

  The icon cluster on the right of the Run row, broken down per operation type.

  [Quick Stats Icons](https://userguide.qualytics.io/operations/runs/deep-dive/quick-stats-icons/)
- **States**

  The five canonical states plus the Warning indicator, and what each one means.

  [States](https://userguide.qualytics.io/operations/runs/deep-dive/states/)
- **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.

  [Lifecycle](https://userguide.qualytics.io/operations/runs/deep-dive/lifecycle/)
- **Available Actions**

  Abort, Resume, Rerun, and Delete: when each one is shown, what it does, and which operation types support it.

  [Available Actions](https://userguide.qualytics.io/operations/runs/deep-dive/actions/)
- **Permissions**

  The user roles and team permissions behind viewing Runs and acting on them.

  [Permissions](https://userguide.qualytics.io/operations/runs/deep-dive/permissions/)

*Last updated: November 6, 2026.*
