> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/profiles/troubleshooting/why-is-some-data-missing-in-your-orchestrations.md).
# Why is some data missing in your orchestrations?
If you are trying to use data sent to Batch through your tagging plan or through the Profile API, but cannot find it, here's a few things you should check.
## 1. Check if the data is active
To check if your attribute or event is active, simply go to **Data** > **Profile Data** and go through the **Attributes** and **Events** tabs: if you can find it in the list, it means the data is active:
You can also check when the data was last received, which sources (iOS, Android, Web, API) it was sent from and when it was created.
{% hint style="warning" %}
If you cannot find the data in your list, **go to step 3**.
{% endhint %}
## 2. Confirm new attributes/events
If you are sending new attributes or events to the dashboard, they need to be confirmed before you can use them in your orchestrations.
To do so, go to **Data** > **Profile data,** and click on the **Attributes** or **Events** tab > **Confirm all:**
## 3. Restore attributes/events
If you could not find your attribute or event in the main list, click on **View Archived**.
All archived data will appear, and you can **Restore** them so they become available in your orchestrations again:
---
# 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://doc.batch.com/guides-and-best-practices/profiles/troubleshooting/why-is-some-data-missing-in-your-orchestrations.md?ask=&goal=
```
`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.