> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zengain-docs/ui-zengain-modules/unfinished-periods-in-engagement-levels.md).
# Unfinished periods in engagement levels
{% hint style="warning" %}
Zengain only shows completed periods in Engagement levels to give useful metrics that the team can act upon—partial periods can be misleading.
{% endhint %}
Zengain will not show engagement insights data for the day, week, or month charts until the first day of the next period, i.e., the system has captured the full period.
In these cases where the data set is incomplete, we show any incomplete periods as a grey chart so you can see that data is coming in but hasn't completed a full cycle yet.
* This grey chart will be based on any activity (event) processed by Zengain during a given period for which we have not yet calculated the Engagement Level.
* Zengain will indicate some engagement, but we won’t be able to say what this engagement level is/will be because the period hasn’t finished yet.
* This doesn’t apply to the Reactivate module, where the subscription has expired, and we do not track any new activity.
---
# 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.nalpeiron.com/zengain-docs/ui-zengain-modules/unfinished-periods-in-engagement-levels.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.
