> 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/managing-workflows-in-collibra/configuration-variables/duration-variables.md).

# Duration variables

Duration variables control time-based behavior for a user task. Collibra generates two duration variables for each user task:

* **\<task id>DueDate**, which shows a due date to the user when the task is presented for information purposes only.
* **\<task id>EscalationDuration**, which sets the time before the task escalates through the out-of-the-box [Escalation Process workflow](/workflows/out-of-the-box-workflows-walk-throughs/escalation-process.md).

Both variables use the ISO 8601 duration format for their values, for example **PT2H30M** for a duration of 2 hours and 30 minutes.

Collibra also supports business day durations. To denote a business day duration, use B instead of P, for example **B7D** for 7 business days or **B20D** for 20 business days. Business day durations do not take weekends into account. If a business day duration ends on a weekend, the duration ends on the first weekday after the weekend.


---

# 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/managing-workflows-in-collibra/configuration-variables/duration-variables.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.