> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/data-testing/cloud-managed-data-contracts/review-checks.md).

# Review checks

After creating and verifying a Cloud-managed data contract, you can review the results of its checks directly in Soda Cloud. The **Checks** page provides visibility into how each check performed during the most recent verification and over time.

<figure><img src="/files/YjGVRIIsTA3q9xYDTk9o" alt=""><figcaption></figcaption></figure>

In the **Checks** page, next to each check, Soda displays the overall verification outcome. The contract can have one of the following states:

* **Passed**: All checks met their defined expectations.
* **Failed**: One or more checks violated the contract.
* **Error**: The contract could not be evaluated due to configuration, connectivity, or runtime issues.

Each individual check is listed with its status. This allows you to quickly identify which rule failed and assess its impact.

### Accessing check results

You can access a check page in Soda Cloud in multiple ways:

* Navigate to the dataset > **Checks** tab > Select the check you want to inspect
* Navigate to the **Checks** page (top menu) and search for the check you want to inspect

### Understanding individual check results

Selecting a check opens its detailed view. This page includes:

#### Historical plot

Check results are stored for each verification run. You can review previous runs to understand how a check has behaved over time. This helps identify recurring issues, assess the impact of upstream changes, and validate that fixes have resolved the problem.

<figure><img src="/files/qmdJPhAgcgynRysr2tnV" alt=""><figcaption><p>Check page for the <code>Email must be valid</code> check in the <code>dim_customer</code> dataset</p></figcaption></figure>

#### Result tab

The **Result** tab provides a concise summary of the outcome of the most recent contract verification for the selected check. It answers the primary question: did this rule pass or fail, and what was the measured value?

At the top of the tab, Soda displays the timestamp of the most recent verification run. Below, a result table summarizes the execution with four fields: the check status, the measured value, the time of execution, and any linked incident.

<figure><img src="/files/Ojk8EAeqYOQ7te3n1FyO" alt=""><figcaption></figcaption></figure>

#### Diagnostics tab

Each check includes a **Diagnostics** tab that explains how the result was computed. Diagnostics provides execution metadata that supports transparency and troubleshooting by showing exactly how Soda evaluated the contract condition.

The tab displays a list of diagnostic properties for the most recent run:

<table><thead><tr><th width="220">Property</th><th>Description</th></tr></thead><tbody><tr><td><code>Failed rows count</code></td><td>The number of rows that failed the check in this run.</td></tr><tr><td><code>Failed rows percent</code></td><td>The failed rows count expressed as a percentage of <code>Check rows tested</code>. Populated when <code>Check rows tested</code> is available.</td></tr><tr><td><code>Dataset rows tested</code></td><td>The total number of rows in the dataset evaluated during the run.</td></tr><tr><td><code>Check rows tested</code></td><td>The number of rows directly tested by the check. For row-level checks (missing, invalid, duplicate), this is populated automatically. For failed rows query checks, this is only populated when <code>rows_tested_query</code> is configured on the check.</td></tr></tbody></table>

<figure><img src="/files/vDOVnq0jCscguDqUKglB" alt=""><figcaption></figcaption></figure>

#### Failed rows tab

When available, failed rows are stored externally in your own data source to guarantee security and privacy. On this tab, Soda provides **failed rows queries** and, if configured, direct access your Diagnostics Warehouse to view failed rows.

{% if !(visitor.claims.plan === 'enterprise' || visitor.claims.plan === 'enterpriseUserBased' || visitor.claims.plan === 'datasetStandard') %}
If [Diagnostics Warehouse](/diagnostics-warehouse.md) is enabled, the **Failed Rows** tab provides access to the specific records that violated the rule. This allows you to:
{% endif %}

{% if visitor.claims.plan === 'enterprise' || visitor.claims.plan === 'enterpriseUserBased' || visitor.claims.plan === 'datasetStandard' %}
If Diagnostics Warehouse [failed row storage](broken://pages/E1KTiEL4c6zytpedbEZg#set-up-diagnostics-warehouse-for-your-data-source) is enabled, the **Failed Rows** tab provides access to the specific records that violated the rule. This allows you to:
{% endif %}

* Inspect the raw data that caused the failure.
* Validate business assumptions.
* Share concrete examples with data producers.
* Accelerate root cause analysis.

When failed row storage is not enabled, this tab remains visible but inactive.

<figure><img src="/files/y7HldKeFNdC5GtYfbda6" alt=""><figcaption></figcaption></figure>

***

Reviewing checks in Soda Cloud closes the feedback loop between **defining** expectations and **enforcing** them. Data contracts establish what “good data” means. Each **check** page shows whether your data currently meets that standard and provides the information needed to investigate and resolve any violations.

***

{% if visitor.claims.plan === 'datasetStandard' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Dataset Standard license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}

{% if visitor.claims.plan === 'enterprise' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Team license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}

{% if visitor.claims.plan === 'enterpriseUserBased' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Enterprise license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}

{% if !(visitor.claims.plan === 'enterprise' || visitor.claims.plan === 'enterpriseUserBased' || visitor.claims.plan === 'datasetStandard') %}
{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).

If you do have a Soda license, make sure to **log in to Soda Cloud in this same browser**.
{% endhint %}
{% endif %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.soda.io/data-testing/cloud-managed-data-contracts/review-checks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.