> 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/soda-documentation/manage-issues/failed-row-samples.md).
# Failed row samples
Learn how to view and configure failed row samples for failed checks in Soda Cloud.
{% hint style="info" %}
Failed row samples are an **opt-in feature** and must be enabled by the Soda support team before it is available in your organization, as it involves **storing a subset of your monitored data in Soda Cloud**.
{% endhint %}
When a Soda scan results in a failed check, Soda Cloud displays details of the scan results in each check's **Check History** page. To offer more insight into the data that failed a check during a scan, **you can enable Soda Cloud to display** **failed rows samples** in a check's history.
When enabled, Soda stores the rows that fail a check in your [**Diagnostics Warehouse**](broken://pages/UZCAHd8ZBgl01336NkZa). If failed row samples are also enabled, Soda uploads a sample of those rows to Soda Cloud, where you can view it in the Failed Rows tab of the check result.
{% hint style="info" %}
The default sample size is **100 rows**. This can be overridden at the data source or dataset level.
{% endhint %}
## Configure failed row sampling
You can enable or disable failed row sampling, and adjust the sample size, at the [**data source**](#at-the-data-source-level) or [**dataset**](#at-the-dataset-level) level.
{% hint style="warning" %}
Failed rows are not emitted for Group By checks.
{% endhint %}
### At the data source level
To configure sampling for all datasets in a data source:
{% stepper %}
{% step %}
In Soda Cloud, navigate to **Data Sources** and select the data source you want to configure. Click on **Edit Diagnostics Warehouse**.
{% endstep %}
{% step %}
Navigate to the **Failed Row Samples** section and select the checkbox "**Allow sending failed row samples to Soda Cloud**".
{% endstep %}
{% step %}
Adjust the sample size.
Failed row samples default to 100 rows.
{% endstep %}
{% step %}
**Save** your changes.
{% endstep %}
{% endstepper %}
### At the dataset level
To override the data source setting for a specific dataset:
{% stepper %}
{% step %}
Navigate to the dataset you want to configure, click on the stacked dots menu > **Edit Dataset**.
{% endstep %}
{% step %}
Navigate to the **Diagnostics Warehouse Configuration** tab > **Failed row samples** section > select the checkbox.
{% endstep %}
{% step %}
Adjust the sample size.
Failed row samples default to 100 rows.
{% endstep %}
{% step %}
**Save** your changes.
{% endstep %}
{% endstepper %}
## View failed row samples
To view failed row samples for a check result:
{% stepper %}
{% step %}
Navigate to the **Checks** page and select a check that has a **Failed** status.
{% endstep %}
{% step %}
At the bottom of the check page, navigate to the **Failed Rows** tab.
If failed row sampling is enabled and rows were collected, the sample is displayed here.
{% endstep %}
{% step %}
\[Optional] Find column.
By searching for a column name, Soda will highlight it in the results to facilitate root cause analysis.
{% endstep %}
{% endstepper %}
## Reroute failed row samples
If the data you are checking contains sensitive information, you may wish to send any failed rows samples that Soda collects to your own Diagnostics Warehouse rather than Soda Cloud. To do so, allow Failed Row Collection while [configuring the Diagnostics Warehouse](broken://pages/E1KTiEL4c6zytpedbEZg#optional-allow-failed-row-collection).
***
{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation. Learn more about [Licensing & documentation access](/soda-documentation/reference/documentation-access-and-licensing.md).
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.soda.io/soda-documentation/manage-issues/failed-row-samples.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
