IMPORT TROUBLESHOOTING
A workout imported, but a metric is missing: what to check
An imported activity can be valid without containing every kind of measurement. Identify the missing input before assuming the whole import failed.
Name the missing result precisely
Write down whether the absent item is a route, a sensor chart, an average or a derived metric. Those results have different input requirements. “The run is missing heart-rate samples” is a more useful starting point than “the data is broken.”
Check the original provider's activity and, when available, the original export. A field displayed by the provider may have been calculated there rather than included in the data transferred to another app. Do not assume identical labels imply identical exported content.
Match the result to its inputs
| Missing result | First evidence to inspect |
|---|---|
| Route map | Recorded positions and route-data access |
| Heart-rate chart | Timestamped HR samples, source and permission |
| Average pace | Usable distance and a defined positive duration |
| Heart-rate cost | Compatible speed and heart-rate summary inputs |
| Early/late efficiency comparison | Suitable aligned streams across both portions |
| Historical trend | Enough relevant activities in the selected date window |
This worksheet describes input needs, not a promise that every recording source supplies each field or that every app uses the same calculation.
Follow one field through the pipeline
Suppose an illustrative imported 8K has distance, time and a route, but no heart-rate trace. Look for heart-rate samples in the original recording, then check the connection's data access. If the source contains only an average, a downstream app cannot truthfully display that as a measured continuous trace.
Garmin's FIT activity documentation distinguishes summary messages from time-series Record messages. That distinction helps explain why having activity totals is not the same as having every supporting stream.
Resolve the specific gap
In Runome, inspect the available source and activity details, then use the relevant connection or support path. Keep a copy of the original export where available. If you send a report, include the recording source, approximate activity date and exact missing metric; provide a file only when it is needed and you are comfortable sharing its contents.
Follow the Apple Health data path for Apple Watch recordings. For summary-only records, the manual-entry guide explains the same evidence boundary. A missing metric can be the correct outcome when its required measurement was never supplied.