This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Automatic Lactate Threshold not working

A few years ago I have switched my running watch from a Garmin Fenix 3HR to a 945.

It seems roughly about the same time, Lactate threshold stopped updating.

I have no data since October 2020  even though under Physiological metrics, auto detection is enabled for Lactate Threshold.

I am also using the HR belt from my Fenix 3HR, which has all the running dynamics data.

I've run all the different distances, from park runs to marathons, at different paces and different intensities, yet no Lactate Thresholds values are populated automatically.

I've seen several posts regarding this but failed to find a solution.

Any help is appreciated.

  • Такая же проблема и у меня. Перепробовал всё... 

  • The auto detect seems to work better after you have had it detected once using the 'Guided Lactate Threshold Test' which after a warmup you are instructed to slowly raise HR into a range every 3-4minutes, the range goes up 5 or 10 bpm every time.  It is a very hard workout... every time i have done it reports after "no threshold  found" , my watch has never notified me of my threshold since i got it more than a year ago.  Threshold Pace is 0:00 and my threshold HR is a manual set , can't find a way to remove it entirely which i'm worried that it is the reason for not auto detect.   Have tired having it too high... and too low.... neither have helped.

    Garmin support said they have had similar reports, asked me to try a few things, didn't help.  

  • Yes, . Some people say that lower the max HR, but I think max HR should be the max HR, not the HR that you usually archive. But yes similar experiences, the older watches detected it much easier, newer not so. Can't remember when this changed and I think I've had my HR settings pretty similar.

    If I look back the data, last time it has been detected in last December with pace and HR! Then previous was just pace in January 2020, then both in September 2019 and then a lot of more measurements.. So 945 came in April so it has been firmware update, so around 2.80 or something.

  • I compared my lactate threshold data to one of my friend's, who switched from a Fenix 5 a while ago, and funny enough, his data stopped at the same time as mine, namely 20th of October.

    Really disappointing that such an important feature is not working on a premium device like the 945, 

  • i've had my 945 for over 2 yrs, and multiple threshold tests have never got anything other than "not detected", plus i've never had any auto detection of LT either. i've given up on it and use a 20+min parkrun PB avg pace & HR as my LT pace and HR, and set my HR zones based on that LT HR

  • I have now tried different solutions from all the different lactate threshold posts i could find, including deleting my profile data, resetting the heart rate zone, enabling and disabling automatic lactate threshold and manually setting the max heart rate to a much lower value.

    Unfortunately that did not improve the situation; after some further 5 and 10kms runs, no change in the lactate threshold values.

  • Just ensure that your max HR is set correctly. I find a 5K race is probably going to make you hit HR max. I have had no troubles with automatic LT readings since I adjusted my Max HR. Almost every run, I have a new "detected" threshold. 

  • Hello,

    I have the same problem: my most recent threshold recorded in GC is from Oct 8th. I was on beta 8.09 and upgraded to 8.20.

    Today I ran a threshold workout where I spent 43% of the time in HR zone 5 and oddly enough, the main benefit displayed is "Tempo" and no threshold was detected. I am training with an HR target and I tried to use running specific HR zones and finally deleted them (only using general zones that are not sport specific)..

    This was working fine before.

    Any advice would be welcome as this is a useful metric,

  • Hello,

    To correct/complete my above post: I had anorther shorter threshold specific training today, I changed the objective from cardio to speed. Still the main benefit displayed is Tempo but a new lactate threshold estimation was finally triggered.

    So nothing wrong to report, I guess I was simply not fast enough