Health Connect not syncing: 7 fixes that work (2026)

Health Connect not syncing problems often have an identifiable cause: missing permissions, battery optimization blocking background sync, or a source app that hasn't reconnected yet. This guide follows a diagnostic order from most to least frequent, without needing to reinstall anything.

First: identify the exact symptom

• •Data never present: the reading app has never received data from Health Connect. Problem: permissions or source app not connected.
• •Data present but delayed (hours/days): sync not real-time. Problem: battery optimization, background sync disabled.
• •Partial data: some metrics yes, others no. Problem: granular permissions missing for specific data types.
• •Duplicate data: same metric appears twice. Problem: multiple sources writing the same type (e.g. Garmin + Samsung Health).
• •Historical gap: data missing for a specific period. Problem: app not connected during that period, or crash.

Fix 1: Check permissions in Health Connect

1. Open Health Connect: on Android 14+ it's under Settings → Security and privacy → Privacy controls → Health Connect; on Android 13 and earlier it's a standalone app (search your installed apps — its app-drawer icon was removed back in 2022).
2. Go to App permissions.
3. Find the app that's not syncing (e.g. FitMesh Sync, Garmin Connect, Samsung Health).
4. Tap the app → verify it has read and write permissions for all data types you expect (Steps, Heart Rate, Sleep, Workouts).
5. If permissions are missing, enable → grant.

Fix 2: Disable battery optimization for the apps involved

Android's battery optimization is the silent killer of background sync. When Android puts an app into deep sleep, it can't read or write to Health Connect. The fix: exclude both the source app (Samsung Health, Garmin Connect) and the reading app from optimization.

1. Settings → Battery → Battery optimization (or 'Power saving' on Samsung).
2. Search for the app (Samsung Health, Garmin Connect, or any other app involved).
3. Select Don't optimize (or on Samsung: tap app name → 'Unrestricted').
4. Repeat for every app in the sync chain.

Fix 3: Force sync from the source app

The most common bottleneck is the watch → phone sync: to save battery, Samsung Health only pulls fresh data from the Galaxy Watch in specific situations documented by Samsung — when the watch reconnects to the phone, when you open the Samsung Health app, or when you pull-to-refresh its home screen. The data type matters too: continuous heart rate is delayed on purpose to save battery (manual measurements sync right away), and sleep data is only processed once the watch reconnects to the phone, which can add further delay. Once Samsung Health actually has the data, it normally writes it to Health Connect fairly quickly, but Samsung doesn't guarantee an exact timeframe — if the numbers look stale, try opening Samsung Health, pulling to refresh, or tapping "Sync now" before assuming something's broken. Garmin Connect writes after each successful watch sync, one-way into Health Connect (it never reads from it). Fitbit is now the Google Health app (since May 19, 2026): configure Health Connect sync from there. Source: Samsung Developers — Accessing Samsung Health Data through Health Connect, Samsung Developers — Managing Sleep Data with Samsung Health and Health Connect, Samsung Developers — Health Connect FAQ and Google Health — Fitbit transition, consulted 2026-08-06.

• •Samsung Health: make sure the watch has reconnected with the phone, then open the Samsung Health app or pull-to-refresh its home screen (Samsung documents these as ways to refresh the data, not just reconnecting). Then go to Settings → Health Connect → verify the link is active and all data types are enabled.
• •Garmin Connect: open the app. Garmin writes to Health Connect after each successful watch sync, one-way into HC (it never reads from it). Check: Garmin Connect → More (☰) → Settings → Health Connect enabled.
• •Google Health (formerly Fitbit): since May 19, 2026 the Fitbit app has become the Google Health app. Open the app → wait for it to sync with the device, then check the Health Connect link in its settings.

Fix 4: Clear Health Connect cache

1. Settings → Apps → find Health Connect (may be under 'All apps').
2. Tap Storage & cache.
3. Tap Clear cache (NOT 'Clear data').
4. Reopen Health Connect and let it reinitialize.

Fix 5 (Samsung): direct Samsung Health → Health Connect connection

On Samsung devices, the Samsung Health → Health Connect connection is authorized separately from the app's general permissions (it's its own link, not just a background-sync setting). If you suspect it's broken, disconnecting and reconnecting it forces a clean handshake:

1. Open Samsung Health → Settings (the exact icon varies by version: look for a profile icon, a hamburger menu, or three dots, depending on your app version).
2. Scroll to Health Connect → tap.
3. Disable the connection → re-enable after 10 seconds.
4. Verify all data types are selected (Steps, Heart Rate, Sleep, etc.).
5. Go back to Samsung Health main screen and wait 1-2 minutes.

Fix 6: Update Health Connect to the latest version

On Android 13 and earlier, Health Connect updates via Play Store like any other app: search for it and update if available. From Android 14 onward, Health Connect is a system module and updates itself, with no manual action needed — what's worth checking at that point is whether the connected apps (Samsung Health, Garmin Connect, or others in your sync chain) have updates available, since those remain regular Play Store apps on any Android version. Source: Android Developers — Migrate Health Connect from Android 13 to 14, consulted 2026-08-25.

1. Open Play Store → tap your profile icon → Manage apps & device.
2. Search for Health Connect and update if available.
3. Do the same for Samsung Health, Garmin Connect, or any other app in your sync chain.

Fix 7: Revoke and re-grant all permissions (full reset)

If none of the other fixes worked, the problem may be in a corrupted permission state. The solution is a full connection reset:

1. In Health Connect → App permissions → find the problematic app.
2. Tap the app → Remove access.
3. Reopen the problematic app → find the Health Connect section in settings.
4. Tap 'Connect to Health Connect' or equivalent → grant all permissions again.
5. Wait 5-10 minutes for the first sync.

When the problem isn't on your phone

If you've tried all the fixes above and the problem persists, it might be a server-side outage of the source app (Samsung Health, Garmin Connect) or a bug in your specific Android version. In that case:

• •Search Reddit (r/GalaxyWatch, r/AndroidHealth) if others have the same problem: a pattern often emerges.
• •Check the source app's status page if available.
• •Report the bug via app feedback.
• •As a temporary workaround, data accumulates locally in Health Connect: it's not lost, just not synced to cloud.

In summary

• •Most sync problems are solved by three actions: check permissions in Health Connect, disable battery optimization for the apps involved, force-open the source app.
• •On Samsung, the specific fix is disconnecting and reconnecting the Samsung Health → Health Connect pipeline from Samsung Health settings.
• •Clearing Health Connect cache does not delete your data: it's safe to do and often fixes corrupted state errors (Android 13 and earlier only).
• •If data is delayed but not absent, the problem is often battery optimization blocking background sync, but it's not the only possible cause.
• •Historical data recovery is not automatic: it depends on the source app (some rewrite history to Health Connect, others don't) and on Health Connect's history-read permission, which without the extended grant only shows the 30 days preceding the app's first permission grant, not a rolling 30-day window from today.