> 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/webhook/delivery-timing-volume-and-ordering/provider-poll-cadence-not-realtime.md).

# What is the webhook delivery cadence per provider?

**Many providers are fetched on a periodic poll schedule rather than in real time**, so a webhook will not fire the instant a user logs or records something.

* SDK-based sources push on change.
* API/cloud providers deliver immediately or on roughly a 10-minute poll.
* Providers like MyFitnessPal fire only when the next poll picks up new or changed data. If nothing changed, no webhook is sent.
* Device-backed types (glucose, blood pressure) also carry device-to-cloud upload latency.

To confirm data exists, check the user's source diary/app directly. If entries appear there, they will be picked up on the next poll cycle. If delays persist, provide the affected user IDs and an example. See [receiving data updates](https://docs.tryterra.co/health-and-fitness-api/managing-user-health-data/receiving-data-updates).


---

# 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/webhook/delivery-timing-volume-and-ordering/provider-poll-cadence-not-realtime.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.