> For the complete documentation index, see [llms.txt](https://support.senar.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.senar.io/senar-analytics/data-missing-from-reports.md).

# Data missing from reports

If you expect specific data to appear in the reports and it doesn't, there are a few things you should check.

* Carefully check the values of each filter. For example, if the filter **2nd Try** is active, the dashboard will remain empty if the students have made only one try. Also pay close attention to the dates in the last filter.
* If the dashboard looks empty at first glance, scroll and check the **Dropout** report at the very bottom of the page.
* Make sure the student's device has been able to connect to the internet since the end of their session so the data could be sent to the SENAR server.


---

# 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://support.senar.io/senar-analytics/data-missing-from-reports.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.