> 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/no-data/connected-but-no-data-arriving/samsung-healthconnect-sdk-pull-required.md).

# Why is no Samsung Health data syncing after I connected?

Samsung Health is a **mobile-SDK integration read through Health Connect** (Samsung writes into Health Connect, the SDK reads from there), so there is no server-side pull. The dashboard 'Get Data' button being greyed out, empty console scopes, and the 'SDK Only' warning are all expected.

Health Connect forbids background syncing, so data only arrives when your app is in the foreground and explicitly requests it via getter calls (`getDaily`, `getActivity`, etc.) with the scheduler enabled at Terra init.

To debug:

{% stepper %}
{% step %}
Confirm `initConnection` returns `success=true`.
{% endstep %}

{% step %}
Verify your app appears in Health Connect's recent access list.
{% endstep %}

{% step %}
Confirm both the source app and your app have permission for each relevant data type in Health Connect (missing permissions silently return empty).
{% endstep %}

{% step %}
Check that data actually appears in the Health Connect app, since Samsung Health does not always write steps, exercise or sleep there.
{% endstep %}

{% step %}
Test with manual `getDaily` / `getActivity` calls.
{% endstep %}
{% endstepper %}

Users can force a sync by opening Samsung Health or Health Connect and pulling to refresh. For more reliable delivery, **use Terra's direct Samsung Health route**, which bypasses Health Connect. See the [mobile-only sources docs](https://docs.tryterra.co/health-and-fitness-api/mobile-only-sources) for setup.