> 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/data-api-sdk/webhooks-dedup-and-sync-reliability/samsung-health-empty-data-not-syncing.md).

# Why does Samsung Health send webhooks with empty data?

When Samsung Health (read via Health Connect) returns empty payloads, work through three things

When Samsung Health (read via Health Connect) returns empty payloads, work through three things:

{% stepper %}
{% step %}
**Samsung Health must grant access to Health Connect**, enabled inside Samsung Health's settings. Your app does not control this.
{% endstep %}

{% step %}
**Health Connect must grant access to your app**, the layer you do control.
{% endstep %}

{% step %}
**Data must actually be in Health Connect on the device.** Check under **Data and Access** in Health Connect; an empty screen means nothing has synced from Samsung Health yet.
{% endstep %}
{% endstepper %}

For the data to reach your destination, either the **scheduler must be on** or you must fetch explicitly:

* With `schedulerOn = true` (default on `initConnection`), the SDK auto-fetches via WorkManager and sends data to your webhook (activity every 20 minutes; daily/body/sleep/nutrition every 8 hours).
* With `schedulerOn = false`, your app must call the getter functions (`getDaily`, `getActivity`, etc.) with `toWebhook = true` to retrieve and send data.

A direct Samsung Health connection (on native Android, the separate `co.tryterra:android-sdk` artifact) is available as an alternative, but requires Samsung business-partner approval. See the [Android SDK reference](https://docs.tryterra.co/reference/health-and-fitness-api/sdk-references/android-kotlin).