Forerunner 970 – Erroneous Max HR Spikes Affecting Training Load & Zone Accuracy

I’ve observed repeated false maximum heart rate detections on my Forerunner 970, even when paired with an HRM-600 chest strap. These spikes often exceed my normal well-rested race max HR (~170–172 bpm at age 61) by 30–40 bpm, briefly showing 200+ bpm before returning to normal. The device accepts these anomalies as valid, instantly raising my Max HR setting and shifting all training zones. This causes underestimation of activity intensity, inaccurate load/recovery guidance, and distorted VO₂max trends.

Recommendation: Please implement a “sanity check” filter before updating Max HR:

  • Ignore values >10% above rolling historical max unless sustained ≥30 seconds
  • Cross-verify spikes between optical and chest strap data
  • Provide a user prompt to accept/reject new Max HR

This would prevent single-reading artifacts from corrupting long-term training data. I can provide FIT files showing the spikes if needed

  • My advice from using Garmins for a long time is to do a hill test to determine your max HR and then set it in Connect and turn off autodetection for Max HR. Repeat the test periodically and adjust as needed. If I don't do this, I will get max HR estimates from doing Zone 2 runs that are ~10 beats higher than the max I have ever achieved running a hill test... I'm not sure how their algorithm works, but IMO the only way to find your real max HR is to go do something hard that gets you within a few beats.