Garmin syncs automatically over a webhook once you link the account. Apple Watch comes in through HealthKit, Galaxy Watch through Samsung Health direct connect. COROS, Polar, and Suunto route through Health Connect on Android. Duplicate runs usually appear when several apps write the same workout. Cleaning up sync sources helps prevent them.
Why the same run looks different in every app
A run from your watch never shows up, or it shows up with a distance that does not match the watch screen. Usually this is not an app bug — it is a question of which path the run took to get there.
Runs arrive one of two ways: straight from the device maker's server, or through your phone's health data store. The first path is closer to the original and keeps details like laps and heart rate zones intact.
Garmin — link the account once
Garmin works by connecting your Garmin Connect account. Once linked, Garmin's server pushes every finished run to TT on its own. You never have to open the app and pull to refresh.
Linking also requests a recent-activity import. The available history and completion time can vary with Garmin permissions and server processing. When Garmin provides lap detail, interval sessions retain per-rep pace and heart rate.
Using Garmin on an iPhone?
Garmin runs can also arrive through the Apple Health app, but linking the Garmin account directly is more accurate. The Health route tends to carry the summary and drop the lap detail.
Apple Watch — automatic through HealthKit
Apple Watch needs no account link. Record a run in the Workout app, it lands in Apple Health, and TT reads it once you grant permission.
If you built an interval session as a custom workout, the segmentation comes along with it. TT reads those workout segments and analyzes work and recovery intervals separately.
Galaxy Watch — Samsung Health direct connect
On Android with a Galaxy Watch, the dedicated Samsung Health connection is the most accurate route. It pulls runs and heart rate straight from Samsung Health without going through Health Connect.
- Open Samsung Health connect from your profile (Android 10 or later)
- Allow permission for exercise records and workout heart rate
- Your last 30 days of runs come in first
- Need more? Pull the last 90 days or the last year on top
When importing history, the last 90 days arrive with laps and heart rate zones; anything older comes in as a summary. Access is read-only — TT never modifies your Samsung Health records.
Direct connect turns Health Connect off
That is deliberate: it stops the same run from arriving twice. So if you also use another watch app like COROS or Zepp, skip direct connect — those runs only arrive through Health Connect. Disconnecting turns Health Connect sync back on, and runs already imported stay put.
COROS, Polar, Suunto, Zepp
These devices write to Android's Health Connect through their own apps, and TT reads from there. Make sure the watch app has permission to write to Health Connect first.
On iPhone the same idea applies through Apple Health. Check that the watch app is allowed to write there.
The same run got saved twice
The most common support question, and it almost always has one cause: several apps are each writing the same run into your health data.
If you record with both a watch and a phone app, or several apps write the same workout back to health data, one run can remain under several sources.
Fix 1 — keep only the original
On iOS, open the workout category in Health and check Data Sources & Access. Adjust source priority or permissions so only the app that records the original workout writes it.
Fix 2 — choose your sync sources
Data management in your profile lets you switch individual apps on and off as sync sources. It filters inside TT without touching system permissions.
TT treats runs with similar start times and distances as duplicate candidates. It keeps one copy and may replace an existing run when a higher-quality source arrives later. Runs whose time or distance differs too much may still need manual review.
Why the original device matters
A run relayed through Strava or Nike Run Club may still include distance and time. Depending on the source and export path, those values can differ and detail may be lost along the way.
- Lost lap splits make it hard to tell an interval session from an easy run
- Without per-segment heart rate, zone distribution cannot be calculated
- Without elevation, there is no grade-adjusted pace
The quality of AI analysis follows the resolution of what came in. With laps intact, it can tell you the pace fell apart in the last 3 km. With only a summary, it stops at "average pace 5:30".
What to look at next
Once runs start arriving, AI running analysis reads each one and builds a coaching report. If you want to know what the metrics mean, see the TT Lab metrics guide.
FAQ
Does linking Garmin import my past runs?
Yes. Connecting the account requests a recent-activity import, and Garmin then pushes each finished run automatically. The available history and completion time can vary with Garmin permissions and server processing.
Samsung Health direct connect or Health Connect?
If you only use a Galaxy Watch, direct connect is more accurate. If you also use another watch app such as COROS or Zepp, keep Health Connect — those runs only arrive through it.
Can I import runs recorded before I connected Samsung Health?
Direct connect imports the last 90 days with laps and heart rate zones, with older runs imported mainly as summaries. Health Connect history depends on the Android version, history permission, and the policy of the app that wrote the record.
Why is every run saved twice?
Most likely several apps are each writing the same run into your health data. Turn off write access for the extra running apps, or pick your sync sources in data management.
Start by connecting your watch
Garmin, Apple Watch, Galaxy Watch, COROS.
Connect once and your next run arrives on its own.