> 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/escalation-process.md).

# Escalation Process

This process is the default mechanism for the escalation of user tasks in workflows.

![](https://2208542399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAeKwSsP1BP6lDDArkTO2%2Fuploads%2Fgit-blob-3254de83f2d6c58890f8b2e76dfafc25f474c6bb%2Fwf_ootb-escalation-process-diagram.png?alt=media)

## Roles

| Role             | Task                                                | Required |
| ---------------- | --------------------------------------------------- | -------- |
| Business Steward | <ul><li>Reassign the task</li></ul>                 | Yes      |
| Business Steward | <ul><li>Receive mail to reassign the task</li></ul> | Yes      |

## Workflow status transformations

No status transformations happen within this process.

## Start the workflow

The workflow starts automatically when a user task is not completed before the escalation deadline. The deadline is determined by the value of the user task **EscalationDuration** variable. For more information about user task generated variables, see [View and edit workflow definition settings](/workflows/managing-workflows-in-collibra/view-and-edit-workflow-definition-settings.md).

{% hint style="info" %}
If the user task has a timer boundary event attached, Collibra does not generate the **EscalationDuration** and **EscalationType** variables, so this workflow does not start. Handle escalation manually through the timer boundary event instead.
{% endhint %}

## Mail escalation

When the escalation type of the user task is set to `mail` via the **EscalationType** variable, each user who is assigned that task is emailed a warning that the task is about to expire and that an action is required from their part. If no action is taken within the time set by the **mailNotifyDuration** variable, the users identified by the **mailToUserExpression** variable are notified via email to reassign the user task.

## Reassign escalation

When the escalation type of the user task is `reassign`, the **mailToUserExpression** users are assigned a task to reassign the escalated user task.

{% hint style="info" %}
Since the "Reassign Task" is a user task, it is also governed by the escalation process.
{% endhint %}

## Resolution

If the escalated user task is resolved before it is reassigned, the process ends.


---

# 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/escalation-process.md?ask=<question>&goal=<user_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.
