> For the complete documentation index, see [llms.txt](https://docs.enlyze.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enlyze.com/en/production-optimization/downtimes/defining-reasons.md).

# Defining downtime reasons

To analyze machine downtimes, downtime reasons must first be configured in the ENLYZE App. Setting up reasons early enables consistent classification when [assigning reasons](/en/production-optimization/downtimes/assigning-reasons.md).

{% hint style="info" %}
What the three downtime categories (Planned, Unplanned, No Production Planned) mean and why assignment matters is explained under [Categories & assignment (Concepts)](/en/concepts/downtimes/categories-and-assignment.md).
{% endhint %}

## Prerequisites

Before defining downtime reasons, [downtime detection](/en/production-optimization/downtimes/detection.md) must be configured for the relevant machine.

## Configure reasons

{% stepper %}
{% step %}

#### Open downtime reasons

Navigate to **Settings > Reasons for downtime**.
{% endstep %}

{% step %}

#### Add reasons

Add downtime reasons under the appropriate category (**Planned**, **Unplanned**, **No Production Planned**). Optionally, organize reasons into groups for better manageability.

<figure><img src="/files/GoCESemwKll3Bi1tEkqu" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Save

Click **Save** to apply your changes.
{% endstep %}
{% endstepper %}

## Related topics

* [Assign reasons to downtimes](/en/production-optimization/downtimes/assigning-reasons.md): Assign reasons to detected downtimes.
* [Categories & assignment](/en/concepts/downtimes/categories-and-assignment.md): Background on the three downtime categories.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enlyze.com/en/production-optimization/downtimes/defining-reasons.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.