> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/device-management/managing-a-workspace/general-settings/device-lifecycle-reports.md).
# Device Lifecycle Reports
Akenza provides *daily* or *weekly* email reports on **device health** at the **Workspace** level, identifying *offline* devices, *weak* signals, or *low battery* levels. Each email includes a comprehensive list of new and ongoing alerts in each category, along with direct links to inspect the affected devices.
You can manage device lifecycle reports in the **Lifecycle report** section of the [General settings](/device-management/managing-a-workspace/general-settings.md) page. Any **Workspace Admin** can turn them on with **Activate lifecycle reports**, choose a **Delivery interval** of *Every day* or *Every week*, and maintain the list of **Report recipients**, which can hold several people.
On workspace creation, the notifications are **enabled by default**, and the workspace creator is set as the default recipient.
### Notification criteria
#### Offline
In order for a device to be marked as offline, the specified offline timeout is compared to the timestamp of the last received message. If the difference exceeds the specified threshold the device is marked as offline.
{% hint style="info" %}
This metric is available for **all devices.**
{% endhint %}
#### Weak Signal
If a device reports a **Signal Quality Indicator (SQI)** of 1, it marked as having a **weak signal**.
More information about SQI can be found in the [Uplink Metrics](/device-management/create-new-device/devices.md#uplink-metrics) section of the device reference.
{% hint style="info" %}
This metric is available for **LoRa devices** only.
{% endhint %}
#### Low Battery
If a device reports a battery level of **25% or lower**, it is counted as having a **low battery**.
The battery level can be calculated in a script or directly sent in the uplink payload (for passthrough devices). More information about Battery Level can be found in the [Uplink Metrics](/device-management/create-new-device/devices.md#uplink-metrics) section of the device reference.
{% hint style="info" %}
This metric is available for all devices, given the uplink payload or resulting sample contains the specified key and value which is used to determine the battery level.
{% endhint %}
### E-mail example
The below E-mail is an example of the lifecycle notification from the akenza office:
An example of a Device Lifecycle Report with one offline device.
---
# 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://docs.akenza.io/device-management/managing-a-workspace/general-settings/device-lifecycle-reports.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.
