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

# Automatic detection

ENLYZE detects downtimes automatically based on a lead variable and a threshold. The configuration is done as part of the [OEE setup](/en/production-optimization/oee.md).

{% hint style="info" %}
What downtimes are, how detection works conceptually, and which lead variables are typical, is explained under [Downtimes (Concepts)](/en/concepts/downtimes.md).
{% endhint %}

## Prerequisites

Before downtime detection works, the following must be set up:

* A **lead variable** with **active** status (e.g. speed, throughput, cycle rate)
* A configured **threshold** and a **minimum downtime duration**

The configuration of these parameters is described under [Setting up OEE tracking](/en/production-optimization/oee.md).

## No data

There are two causes for periods without data:

* The machine was turned off and is not sending data.
* There is a **connection problem**.

### Common causes of connection problems

Connection problems mean that data is expected but not arriving. The most common causes:

* The connection between the Edge Device and the data source (PLC, sensor) was interrupted (e.g. a cable was disconnected)
* The Edge Device lost power
* Firewall settings were changed from the [original configuration](/en/connect/security.md)

{% hint style="warning" %}
If the connection to the data source or the power supply was interrupted, any unrecorded data is lost. If the Edge Device still has a connection to the data source, it can buffer up to one month of data locally. Once the connection to the cloud is restored, all buffered data is delivered.
{% endhint %}

## Related topics

* [Setting up OEE tracking](/en/production-optimization/oee.md): Configure downtime detection.
* [Defining downtime reasons](/en/production-optimization/downtimes/defining-reasons.md): Set up the reasons catalogue.
* [Assign reasons to downtimes](/en/production-optimization/downtimes/assigning-reasons.md): Assign reasons to detected downtimes.
* [Common issues](/en/help/common-issues.md): Further help with connection problems.