Possible unit-conversion bug: Trail Run lap average cadence appears approximately lower than distance/time/stride-derived cadence by a factor near yards/meters. With lap time 9:58, lap stride length 0.79 m, and lap distance 0.60 mi, expected cadence is about 122.6 SPM. Reported lap cadence is 113 SPM. 113 / 122.6 = 0.921, close to 0.9144. If internal distance/rounding puts the lap at about 0.6046 mi, the ratio is exactly the yard/meter factor.
Exact numbers for an example from this very morning:
Lap distance: 0.60 mi; independent Google Earth distance: 3121 ft / 951 m.
Lap time: 9:58.
Lap stride length: 0.79 m.
Reported lap average cadence: 113 SPM.
Expected cadence from distance/time/stride: 951.3 / (9.9667 × 0.79) = 120.9 SPM.
Using 0.60 mi exactly gives 122.6 SPM.
Reported/expected ratio is about 0.92–0.94, near the yards/meters factor 0.9144.
Real-time cadence and cadence graph appeared near 120 SPM, and metronome was set to 60 BPM, one beat every other step.
Recorded on Fenix 8. Same error in connect app and website. Website screenshot: Note lap 2:
I tried also to report as bug, but nobody "answered" the product support chat. So I throw it out here as hail mary.