APPLE WATCH DATA
Apple Watch to Runome through Apple Health: follow the data
Apple Watch data reaches Runome through Apple Health. Check each stage separately so a missing metric does not turn into a guessing exercise.
Start with the workout record
First confirm that the intended workout exists in Apple's own activity history. Match its date, start time, duration and distance. Then check that the relevant data are available in Health before expecting a downstream app to read them.
This workflow describes Runome's Apple Health connection for Apple Watch data. It does not imply a native Runome watchOS recording app. Keep the recording device and the app doing the later analysis distinct when describing the setup.
Permissions are specific to data categories
Apple's Health-data guide explains how to manage app access and inspect data sources. Check the categories you intend to share, including relevant workout and sensor data. A visible workout summary does not by itself establish that every supporting sample is accessible to another app.
Only grant the access you choose to use. Avoid repeatedly deleting and recreating an activity while investigating a permission issue. Keep the original record and change one relevant setting at a time so you can tell what affected the result.
Trace one illustrative workout
| Stage | What to compare |
|---|---|
| Recorded workout | Date, start time, duration and distance |
| Health data | The workout and the related data categories |
| Runome activity | Matching summary and source information |
| Detailed analysis | Which streams actually appear |
| Unresolved gap | The specific missing field and where it stops appearing |
Imagine the workout and route arrive, but heart rate does not. That is a narrower problem than “nothing synced.” Check the heart-rate source and access specifically. If the workout itself is absent upstream, there is no reason to expect a downstream analysis to reconstruct it.
Inspect duplicates before removing anything
If more than one service contributed data, compare the original sources before deleting a record. Apple Health's source-priority controls concern its own data organization; do not assume they describe how every other app handles duplicate workouts.
Use Runome's compatibility page for the supported connection context and the missing-metric guide for the next checks. A support request is more useful when it names the missing field and the stage where it disappears, while keeping unnecessary personal health or location data out of the message.