# Manage data quality issues

**Detecting a data quality issue is only the start**. The harder part is the work that follows: knowing **which** issues matter, **who** should look at them, **what** the business impact is, and **how** to drive them to resolution before downstream consumers are affected.

**Soda Cloud** gives data and platform teams **a single place** to make that work manageable **at scale**, turning thousands of individual check results into a coherent operational picture of data health across your organization.

## Soda for issue management

Most data quality tooling stops at "the check failed." That leaves the rest of the workflow—triage, ownership, communication, and resolution—scattered across Slack threads, tickets, and tribal knowledge. **Soda closes that gap**.

{% columns %}
{% column %}

#### See the whole estate at a glance

Track the health of every onboarded dataset and every active check from one view. Spot trends, identify the datasets most at risk, and measure how data quality is evolving over time across teams, domains, and data sources.
{% endcolumn %}

{% column %}

#### Focus on what matters to your team

Slice the picture by domain, owner, criticality, environment, or any custom dimension that reflects how your organization actually works. Save the views your team relies on and share them with stakeholders.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

#### Investigate without leaving the platform

When something fails, drill from a high-level health score down to the dataset, the column, the check, and the historical trend behind the failure, with the diagnostic context needed to understand scope and impact.
{% endcolumn %}

{% column %}

#### Get the right people involved, fast

Route alerts to the teams and channels that own the affected data, open incidents that track resolution to closure, and keep a record of what was broken, what was done, and why.
{% endcolumn %}
{% endcolumns %}

## Soda Cloud capabilities

Soda Cloud is the layer that sits on top of your data quality checks, whether they're authored as data contracts, monitored as metrics, or run from [Soda Core](https://github.com/sodadata/soda-core), and turns them into an **operational workflow**.

At a high level, teams use it to:

* **Monitor data health across the organization** with executive-level dashboards covering scan activity, failing checks, and overall health scores, filterable by the dimensions that matter to your business.
* **Browse datasets and checks** with rich filtering, search, and saveable views, so each team can carve out the slice of the estate they're responsible for.
* **Tag datasets and checks with custom metadata** (domain, criticality, data layer, owning team, sensitivity) and use that metadata to drive filtering, reporting, and alert routing consistently across the platform.
* **Analyze check and monitor results over time** with historical trend views and per-check-type diagnostics that surface the *why* behind a failure, not just the *what*.
* **Send the right alert to the right place** through a notification system that targets recipients based on the properties of the affected data, rather than blasting every failure to a single channel.
* **Run investigations as incidents** with assigned ownership, status tracking, resolution notes, and integrations into the tools your on-call and operations teams already use.

## Collaboration across roles

Issue management in Soda is designed around the reality that **data quality is a team sport**. Data engineers, platform owners, analysts, and business stakeholders all need different views of the same underlying signal.

{% hint style="info" %}
Saved views, custom attributes, and scoped notification rules let each persona work from a **tailored slice of the same source of truth**, without forking dashboards or duplicating logic.
{% endhint %}

### Integrate Soda with your existing tools

The built-in dashboards cover the most common needs, but every organization eventually wants to roll data quality metrics into its own reporting layer. **Soda exposes its data through a public REST API**, so you can pull health scores, check results, and incident data into **Power B**I, **Tableau**, **Looker**, or any internal tool your business already trusts.

## Soda Core vs Soda Cloud

**Soda Core** gives you a powerful, scriptable way to run checks against your data and get pass/fail output wherever you invoke it: perfect for **CI pipelines**, **orchestrators**, and **local validation**.

**Soda Cloud provides the layer above**: cross-team dashboards, historical trends, routing of alerts to the right recipients, incident workflow, and shared metadata model. Those are the problems Soda Cloud solves once a single team's checks become an organization's data quality program.

If you've outgrown the "check ran, here's the result" loop and need to manage data quality as an ongoing operational discipline across many teams and many datasets, the Soda Cloud features are what makes that step possible.

<br>

***

{% if (visitor.claims.plan === 'datasetStandard')
%}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Free 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).
{% endhint %}
{% endif %}


---

# Agent Instructions: 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:

```
GET https://docs.soda.io/manage-issues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.