# Incidents

Incidents help you track, investigate, and resolve data quality issues when they occur. An incident is created when a data issue, such as a failed or warning check, has been confirmed and assigned to someone for resolution.

To create or update an incident, the user has to have "Manage Incidents" on the related dataset.

## How to create an incident

{% hint style="warning" %}
Only users with the **Manage Incidents** permission for the dataset can create or edit incidents. All users with access to the dataset can view existing incidents. Read about [global-and-dataset-roles](https://docs.soda.io/organization-and-admin-settings/global-and-dataset-roles "mention")
{% endhint %}

You can create an incident directly from a check result when an issue has been identified:

{% stepper %}
{% step %}

#### Navigate to a check page

On a check page, use the **context menu** to select **Create Incident**.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2Fbis8eTZy4ytgaWSmflkC%2FScreenshot%202025-05-29%20at%208.11.24%20PM.png?alt=media&#x26;token=5615ff22-d04d-4ce3-b9e6-5aeab01d5d95" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Describe the incident

Provide a **name** and **description** for the incident.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FYUjxVp1NXF0ji9SrrXKL%2FScreenshot%202025-05-29%20at%208.12.15%20PM.png?alt=media&#x26;token=6948e836-e620-4810-9fb2-be5302255924" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Connect the incident to check results

Select one or multiple **related check results** that you want to associate with the incident.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FTYkuMOVIFoTON2zkPlHd%2FScreenshot%202026-01-26%20at%204.09.37%E2%80%AFPM.png?alt=media&#x26;token=edf86990-0330-4e1f-bdc7-7c07950ee2a2" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Create the incident

<i class="fa-octagon-check">:octagon-check:</i> Click **Save** to proceed
{% endstep %}
{% endstepper %}

## View incidents for a dataset

Once created, the incident will appear in the **Incidents tab** of the corresponding **Dataset Page**

It is possible to filter incidents based on lead, status, reporter, and severity.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FsEZbveilg5VRMlNcQXMp%2Fimage.png?alt=media&#x26;token=cafd7acb-d8d2-4186-9690-cc9db8f3c2a1" alt=""><figcaption></figcaption></figure>

## View incidents across the organization

Incidents can also be seen in a central place in Soda Cloud. In the top navigation, click on Incidents to see all the incidents of the organization.

Use the filters and the title search to find relevant incidents.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FSyc4kXGFypFlSwbYmBPb%2Fimage.png?alt=media&#x26;token=dce628e3-df4b-4c6b-98c3-c64959df098b" alt=""><figcaption></figcaption></figure>

## Updating an incident

### Assign a lead

Every incident requires a **lead:** the user responsible for resolving the issue.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2F3rDRBTHpSxqqFbdlRDD0%2Fimage.png?alt=media&#x26;token=690057f2-aab4-417d-8315-ed19928192c3" alt=""><figcaption></figcaption></figure>

### Update status

Track progress by updating the incident’s status as the investigation and resolution evolve.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FNnGNdPg0FtAf0wC08yWi%2Fimage.png?alt=media&#x26;token=a1d727e7-fbc3-4453-bf6b-f1194ab9137f" alt=""><figcaption></figcaption></figure>

### Add a resolution note

When marking an incident as **resolved**, a resolution note is mandatory to document what was done.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2F6rGdlsd10Od3HVaLRswL%2Fimage.png?alt=media&#x26;token=8a662186-dd8b-4218-919d-ffe6f92d3671" alt=""><figcaption></figcaption></figure>

### Include more check results

If new results are failing, you can include them in the incident.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2F4QhG2bY1Aro61Co3eYfM%2Fimage.png?alt=media&#x26;token=062f2e8d-4a96-4d2f-ac0f-64b014ca4d64" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
After any changes, click **Save** or **Resolve** on the top right corner to apply them.
{% endhint %}

## Integration with external systems

You can integrate incidents with Slack, MS Teams, or other external systems using Soda’s **webhook** capabilities or the **Incidents API**.

> Learn on how to integrate with Soda: [Integrations](https://docs.soda.io/integrations).

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2Fe1qtfzmyPAQpomswkZTC%2Fimage.png?alt=media&#x26;token=5bae36ba-064b-4d4f-8e4d-2178a72e9861" alt=""><figcaption></figcaption></figure>

<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-and-licensing](https://docs.soda.io/reference/documentation-access-and-licensing "mention").
{% 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-and-licensing](https://docs.soda.io/reference/documentation-access-and-licensing "mention").
{% 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-and-licensing](https://docs.soda.io/reference/documentation-access-and-licensing "mention").
{% 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-and-licensing](https://docs.soda.io/reference/documentation-access-and-licensing "mention").
{% 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/incidents.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.
