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.

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.