> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/out-of-the-box-workflows-walk-throughs/dq-incident-triage.md).

# DQ Incident Triage

This workflow reviews an incoming Data Quality event and asks the assigned reviewer to confirm whether it should be logged as a Data Quality Issue. If confirmed, the workflow creates the issue linked to the affected asset.

<figure><img src="/files/UCtlsUWC3KPsNbNtjtRs" alt="A workflow diagram showing three steps: Parse Trigger reads the Data Quality event and resolves the reviewer via the recipient cascade; DQ Incident Review presents the event summary to the reviewer, who confirms or dismisses; if confirmed, Create Issue creates a Data Quality Issue linked to the affected asset"><figcaption><p>DQ Incident Triage workflow</p></figcaption></figure>

## Roles

| Role     | Task                                                               | Required |
| -------- | ------------------------------------------------------------------ | -------- |
| Reviewer | <ul><li>Confirm whether the event should become an issue</li></ul> | Yes      |

The reviewer is the DQ manager resolved from the event payload. If no DQ manager can be resolved, the workflow falls back to the configured `FALLBACK_ASSIGNEE` user, which is **Admin**.

## Start the workflow

The workflow starts automatically when one of the following Data Quality start events is emitted:

* **Data Quality Job Failed**: A Data Quality job fails to run.
* **Data Quality Job Condition Breached**: A Data Quality job run completes but a configured condition is breached, for example the quality score falls below a configured threshold.
* **Data Quality Monitor Event**: A Data Quality monitor changes state, for example from passing to breaking.

For events to trigger this workflow, the DQ job must be in Event Emission mode with the corresponding event toggle enabled.

{% hint style="info" %}
Configuration-change events, where the `changeType` process variable is set, are silently ignored. The workflow ends without creating a review task or an issue.
{% endhint %}

## Review the incident

The reviewer receives a **DQ Incident Review** task containing a summary of the Data Quality event, including the job name, event type, and event-specific details such as failure information, quality score and breached conditions, or monitor state change details.

The reviewer evaluates the event and decides one of the following:

* **Confirm**: A Data Quality Issue is created.
* **Dismiss**: The workflow ends without creating an issue.

## Outcome

If the reviewer confirms, the workflow creates a Data Quality Issue in the Data Helpdesk linked to the affected asset. The [Issue Management](/workflows/out-of-the-box-workflows-walk-throughs/issue-management.md) workflow then starts automatically and manages the full governance lifecycle of the issue, including review, approval, and resolution.