> 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).