> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/no-data/delivery-delays-lag/oura-app-vs-cloud-delay.md).

# Why is my Oura data late, and can I force a sync?

Oura's mobile app and cloud are separate systems, and **Terra can only access cloud data**. Data visible in the app has not necessarily synced to Oura's cloud yet.

Terra polls Oura roughly every 10 minutes, so multi-day delays originate on the provider side (the Oura app syncing to its cloud late).

To check: **verify availability at Oura's web portal**, which is the source of truth. If the data is missing there too, the delay is between Oura's app and cloud.

Some delay is normal, and there is no way to force Oura to sync at a specific time.


---

# 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:

```
GET https://docs.tryterra.co/faq/help-topics/no-data/delivery-delays-lag/oura-app-vs-cloud-delay.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.