> 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/help-center/help-topics/no-data/webhooks-background-delivery-stopping/healthconnect-no-background-delivery.md).

# Why am I getting auth but no Health Connect data webhooks?

Whether Health Connect data flows automatically after authentication depends on the scheduler.

Whether Health Connect data flows automatically after authentication depends on the **scheduler**.

* With `schedulerOn = true` (the default on `initConnection`), the Android SDK uses **WorkManager** to periodically fetch new data and send it to your webhook **automatically**. Default intervals: activity every 20 minutes; daily/body/sleep/nutrition every 8 hours (configurable server-side).
* With `schedulerOn = false`, nothing is fetched automatically. Your app must explicitly call the getters (`getDaily`, `getSleep`, `getActivity`, etc.) with `toWebhook = true` to deliver payloads to your webhook.

If you have auth but no data webhooks, check the common gotchas:

* Confirm `schedulerOn` was `true` at `initConnection`, or that you are actually calling the getters.
* Confirm the user granted Health Connect's background-read permission. Without it, automatic sync doesn't run in the background. This needs Android SDK 1.7.3 or later, and `enableBackgroundDelivery` asks again if the user declined.
* In release builds, code shrinking (R8/ProGuard) can strip the classes the SDK needs to query Health Connect. Add the Terra ProGuard keep rules.
* Build a custom dev client / EAS Build (not Expo Go), since the SDK is a native module.
* On reconnect, the SDK re-enqueues the WorkManager fetch jobs only if `schedulerOn` was enabled.

See the [Android SDK reference](https://docs.tryterra.co/reference/health-and-fitness-api/sdk-references/android-kotlin).