No more threshold lactic calculated since 3 weeks

TomFR said:

whats happened ? Known bug ?

No bug at all. Garmin tells us it is the new Improved Lactate Threshold Measurement Feature    

TomFR said:

the worst is that on 15th december I did not run

I run daily, and with the former LTHR detection I used to receive regular updates from harder runs. Doing an interval training guaranteed the detection. Since the new LTHR detection method was implemented, I no more get practically any updates. Hard runs and interval runs do not help. I even tried mimicking the former LTHR Guided Test, and it did not help either.

In the last two weeks I did not run on 12/26, 12/31, and 1/4 at all, and just like you, I got the LTHR detection exactly on those days. So it looks like you must not run at all to get the estimate 

What is even weirder, is the Threshold Power - when I enable it on the LTHR graph, I get some values on other days than the pace/hr detections, and there is no HR or pace associated with it. It is unclear to me how the watch can estimate or detect the threshold power, without knowing the threshold HR, and why it is logged without the pace value too.

Unfortunately there is no feedback from the developers, so nobody knows how is it supposed to work (except of the very sketchy description in the above mentioned article).

Thanks for reply. I totally agree and did the same observations.

They’ve got an issue/bug for sure.

I follow up all my stats for so many years, I know when it does not work…

Ive recently rated very bad this Garmins Forum because even with users like us who know very well Garmin and report an issue, we never get official answers, even a simple «  we are working on it »…

Im Incident Manager on a big french IT firm and that is unbelievable to be let like this for weeks and more…

TomFR said:

we never get official answers, even

That’s because this is a peer-to-peer forum. If you want answers/assistance contact Garmin Support directly. 

Hi, i just check, and despite i'm sure that this week is saw the "new" lactate threshold message after saving my trail run activity, i'm too without statement since .... 3 weeks 

It could coïncide with 19.41 release the 11 December. https://forums.garmin.com/beta-program/fenix-7-series/f/announcements/397695/beta-version-19-41---now-available-ota-for-all-models

But i check my activities and 11/12 i did a run with 19.40beta, then 13/12 a Trail Run with 19.41Beta ...

Yesterday I rolled back to 17.28 which is IMO the last good enought software from Garmin. Today I ran and guess what? Got new LT detection! With 19.41 software I hadn't that for 6 last weeks of trainings! The last detection was 24.11.2024 on 19.34b.

And my watch didn't restarted during the run as did on 19.41 software.

My F7X SS is the last Garmin I bought. Never again...

Here is a graph of my LTHR over the past 4 weeks. Fenix 7S Pro Solar / 19.41.

It's obviously still working under some circumstances. I was running every day in December, though clearly didn't always trigger the calculation. 

Yes, I know that LT will not be detected on every run.  But I know myself, and within this 6 weeks was several runs, when LT should be detected - but it wasn't. Changing the software to the older one brought immediate results.

I go for a run 5 times a week, following the Garmin Coach suggestions and my running LTHR has not been adjusted since november 30th of last year. The Power value is updated twice after that date, but Pace and HR are not. It might be that there is no change in the LTHR, but still then I would expect that it detects my LTHR and report to me that nothing has changed. 

In my case it is opposite.
Before software change I was not able to get LTHR, now I'm getting it my every outside run.
At the beginning values were odd (I had almost two months break and it might be cause of it) but last run I did generates LTHR at previous level.
All these runs were rather slow, classified as BASE runs.

I'm using Descent MK3i with 19.34 firmware.

Hi you know Ive opened a ticket just after your post, and guess what… no new yet….

it is a notable bug.. in progress for weeks. Garmin should communicate about it, but still nothing ! Maybe dev dont work on it… frankly Im very disappointed… after many years with them I think I will test Coros.