> 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/dq-incident-triage-configuration.md).
# DQ Incident Triage configuration
Access the workflow configuration via **Settings** → **Workflows** → **Definitions** → **DQ Incident Triage**.
DQ Incident Triage configuration page
## Description
Reviews an incoming Data Quality event and asks the assigned reviewer to confirm whether it should be logged as an issue. If confirmed, creates a Data Quality Issue linked to the affected asset.
## Applies to
This workflow definition applies globally and is not restricted to a specific asset type.
## Configuration variables
You can edit the configuration variables directly from the workflow definition page by clicking **Edit** in the upper-right corner of the variables table.
The available configuration variables are automatically generated. For more information about user task generated variables, see [General workflow settings](/workflows/managing-workflows-in-collibra/view-and-edit-workflow-definition-settings.md).
{% hint style="success" %}
You can configure a `FALLBACK_ASSIGNEE` variable in the script to a [candidate user expression](/workflows/designing-workflows/processes/shape-repository/user-task/candidate-user-expressions.md). It represents the user assigned as the reviewer when no DQ manager can be resolved from the event payload. Update this value before publishing the workflow to a production environment. The default value is `user(Admin)`.
{% endhint %}
## Start event
The DQ Incident Triage workflow starts automatically when any of the following start events is emitted:
* Data Quality Job Failed
* Data Quality Job Condition Breached
* Data Quality Monitor Event
For more information about these start events and their process variables, go to [View and edit workflow definition settings](/workflows/managing-workflows-in-collibra/view-and-edit-workflow-definition-settings.md#start-event).
## Roles
The roles define the permissions to manage the workflow.
| Action | Roles |
| ------------------------------------------------------------------------------------------- | ----------------------------------------- |
| Start workflow. An action item with the start label is available to users with these roles. | There is no out-of-the-box default value. |
| Stop workflow. The option to cancel the workflow is available to users with these roles. | There is no out-of-the-box default value. |
| Reassign tasks. The option to reassign the task is available to users with these roles. | There is no out-of-the-box default value. |
## Other
| Setting | Enabled |
| ------------------------------------------------------------------------ | ------- |
| Any user can start the workflow. | No |
| Perform candidate user check on workflow start. | Yes |
| This workflow can only run once at the same time on a specific resource. | Yes |
| Lock resource. | No |
| Show in global create. | No |
---
# 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://developer.collibra.com/workflows/out-of-the-box-workflows-walk-throughs/dq-incident-triage/dq-incident-triage-configuration.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.
