Health Connect Duplicate Steps and Workouts: 7 Fixes

First distinction: duplicate records do not always mean a duplicate total

Health Connect preserves each record's origin: the source app, device, time interval, and recording method. Two apps can therefore each show a Steps entry for the same interval without necessarily doubling the displayed total. According to the Android aggregate-data documentation, the Aggregate API deduplicates Activity and Sleep data according to the user's source priorities. The original entries remain attributed to their respective sources.

This distinction prevents the most common bad advice: deleting everything as soon as two records appear. First determine whether you are seeing multiple source entries, an inflated total, or a complete workout duplicated as a second session. Each problem has a different fix.

Seven-step procedure to remove duplicates without losing data

1. Open Health Connect from the correct path

On Android 14 and later, open Settings → Security & privacy → Privacy controls → Health Connect. On Android 13 and earlier, Health Connect is a separate app available from Google Play and can also be opened through Settings → Apps → Health Connect → Open. Labels can vary slightly by manufacturer, but the relevant sections are App permissions, Data and access, Recent access, and Manage data.

2. Find which app wrote each copy

Open Recent access → See all recent access to see which apps read or wrote data during the last 24 hours. Then open Data and access, choose the category and data type, and select See all entries. Health Connect identifies the source of each record. Google's official guide to finding Health Connect data confirms that you can inspect individual entries and app permissions before changing anything.

3. Set source priority for Activity and Sleep

Open Manage data → Data sources and priority, choose Activity or Sleep, and drag the preferred app to the top. Google states that when values from different apps conflict, the app higher in the list receives priority. You can also exclude a source from aggregate totals without deleting its stored records; see Manage your Health Connect data.

Check steps recorded by the phone itself

Since June 2026, compatible devices running Android 14 or later can have Health Connect record steps directly from the phone's step sensor. The phone appears as a separate source and has the lowest priority by default. To exclude it, open Health Connect → Devices → phone name → Steps and turn off step tracking, or remove the phone from Activity totals. Google documents both phone-step attribution and the controls available to users.

4. Revoke only the redundant write permission

If an app should no longer publish steps or workouts, open App permissions → app name and turn off write access for that data type. Do not revoke every permission automatically: an app may need to read steps without writing them back. Google's connected-app permissions guide distinguishes revoking access from deleting data that is already stored.

Removing an app from "Data Sources and Priorities" merely excludes it from the total of the category. The app can still write. Disabling the write permission, on the other hand, prevents new records but does not delete existing ones. These are three distinct operations: priority, permission, and deletion.

5. Break the loops between direct integration and Health Connect

The typical duplicate-workout problem is a sync loop: service A sends a session directly to service B, while the same session also reaches Health Connect and B imports it again. Another loop occurs when an app reads a record from Health Connect and writes it back as though it were new. The practical rule is simple: keep one inbound path for each destination and data type.

6. Remove the erroneous copies only after stopping the source

Health Connect lets you delete one entry, an entire data type, a category, a time range, or all data written by a specific app. The safest path is Data and access → category → data type → See all entries, then delete only the confirmed bad copy. For a broader cleanup, use App permissions → app → Delete app data and choose the affected period.

Google's official deletion instructions warn that the source app or device may retain its own copy. Deleting a record from Health Connect does not automatically remove it from the manufacturer's cloud. If the writer remains active, that copy can sync back.

7. Force a new synchronization and verify the final total

Open the source app first, wait for it to complete the wearable synchronization, then reopen the reading app. Check Recent Access and individual entries again. For Activity and Sleep, the aggregated total updates when you change sources or priorities; for workouts, ensure there is only one session and that duplicates are not recreated.

Why steps can be correct while workouts remain duplicated

Steps are cumulative data that can be read through the Aggregate API, where Health Connect applies source priority to Activity totals. A workout is instead a session with a start time, end time, exercise type, optional route, and related records. Two apps can create separate sessions describing the same run, each with a different identifier and origin.

For developers, Android recommends a stable `clientRecordId`. If the same app retries the same record, Health Connect can ignore the duplicate or update the existing version. This prevents retry duplicates from one integration, but it does not prove that records from two different apps describe the same activity. Android documents the distinction in its guide to workout experiences with Health Connect.

How FitMesh handles overlapping sources

On Android, FitMesh reads steps through Health Connect's native aggregation, so the result benefits from the user's Activity source priority. For other data, it applies controls in its reading and dashboard layers: removing identical records, selecting a source for cumulative metrics, reconciling overlapping sleep sessions, and removing cross-source workouts with the same start time, end time, and exercise type.

FitMesh can therefore show a coherent view even when Health Connect still contains records attributed to multiple apps. It does not, however, clean the Health Connect database for every other application. If another app still displays a duplicate, correct the source priority, write permission, or sync path at its origin.

Checklist for preventing duplicates with multiple wearables

1. Choose a primary source for Activity and one for Sleep.
2. Let a single companion app write each type of data when a secondary copy is not needed.
3. Avoid having an app bridge use Health Connect as both the source and destination for the same data simultaneously.
4. When you directly connect two services, disable the equivalent import through Health Connect in the target app.
5. Check Recent Access after every new integration.
6. Before changing permissions, note the configuration and save any important exports.
7. After making the change, verify both the individual items and the total displayed by the app you are actually using.

Sources and verification status

Last verified: July 13, 2026. Primary sources: Health Connect aggregation and priority, data-source management, data and Recent access inspection, connected-app permissions, data deletion, and workout-session records. Statements about FitMesh were verified against the app repository rather than inferred from marketing material.