Lactate Threshold bug in GC

@Joseph

please see attached fit file and Connect view.

Thx

Where is Lactate Threshold

I may be being very silly here but where the only place i find my LT is on my Fenix 3. I cannot find any mention of it on GC (both mobile and online). Any ideas?

@Andyt5,

Thank you for attaching the FIT file, unfortunately that FIT file does not contain a new LT value and this is why your Reports have not updated to display a correct LT value. Your watch will either detect a new LT value over the course of your normal training or you can do a guided test.

I may be being very silly here but where the only place i find my LT is on my Fenix 3. I cannot find any mention of it on GC (both mobile and online). Any ideas?

You can view your LT Report in Garmin Connect by clicking the 3 line icon and then selecting Reports for the menu list. Then under the Running section you will have an option for Lactate Threshold.

I do apologize for the silence on my end regarding this issue. There was a scheduled Garmin Connect update last week that got delayed until today. It was pushed out this afternoon, and the expectation is that any new LT value that is uploaded will be correct. What is still being worked on, and I am waiting for an update, is the progress on correcting the previous values. When I have new information on this I will update this thread.

@GFM1011, I just wanted to confirm that yesterday (for the first time since the GC update), my 735XT posted correctly an LTHR measurement; thank you so much for fixing that!

Now unfortunately the previous measurements are still messed up and here is how the widget looks like currently :-(

@Joseph
thanks for watching the fit file.:)

For my understanding, the LT and Pace will only be updated in Connect when watch values are changed?:confused:

I don't understand, my LT and pace in watch in normal training do always fluctuating a bit.:(

Can I push a manual update?

Please explain.

Just to give everyone an update. The Garmin Connect team is still working on a process for correcting the incorrect LT values. They did not provide a timeline, but did ensure that they are working on this. I do apologize that I don't' have anything more specific, but wanted to provide the information that I do have at this point.

@Joseph
thanks for watching the fit file.:)

For my understanding, the LT and Pace will only be updated in Connect when watch values are changed?:confused:

I don't understand, my LT and pace in watch in normal training do always fluctuating a bit.:(

Can I push a manual update?

Please explain.

Your device will track Lactate Thresholds two ways. There is an option to allow the device to track it automatically overtime. If you do it this way then it will take several runs, at specific thresholds based on heart rate zones, to get a new value.

The watch can also do a structured Lactate Threshold test. Typically following the test is the best way to obtain a new LT value. The FIT file that you shared did not contain a new LT value, which indicates that this particular run didn't meet the criteria for a new LT value.

If you are able to do the structured test you will hopefully get a new value to upload to Garmin Connect so that the most recent value is not displaying incorrectly.

Just to give everyone an update. The Garmin Connect team is still working on a process for correcting the incorrect LT values. They did not provide a timeline, but did ensure that they are working on this. I do apologize that I don't' have anything more specific, but wanted to provide the information that I do have at this point.

@GFM1011, thank you for the update but this is so very disappointing!

I feel this is part of a bigger issue though. Spurious "bad" values do exist in other measurements in addition to the systematic LTHR problem this thread is about. For example, one time I took off my HRM-Run while the 735xt was still recording, and somehow it generated some 240bpm erroneous HR values. I ended up saving the run (because I needed the track) and what do you know, the MaxHR report updated to reflect the erroneous value. Of course this was partly my fault for removing the strap but also Garmin's problem since somehow the HRM-Run generated really high HR values instead of, well, zero.

What I am trying to say here is that in a perfect world, all recordings would be great, but in practice (and especially given Garmin's bug-prone software) bad values do creep in our measurements. Is it about time that Garmin would allow us to edit those values ourselves thus at least mitigating some of the frustrations?

In the case of this thread, if Garmin where to come out and tell us what sort of "bad equation" was used to update the LTHR with such super-low pace values, then each one of us could reverse-calculate the proper value and perform the fix.

I don't know, I am just very frustrated about this and I am trying to be creative towards a solution.

@GFM1011, one more suggestion.

Maybe your developers can simply adjust the Pace axis scale to something more "human" (there is no way anyone runs 1:10min/mile runs). If you adjust the pace axis scale to +-1min/mile around the median of all recorded LTHR values, then at least the "bad" values will be out of range and not be displayed until you fix them. This way we could still browse our pre- and post-bug measurements and still get an idea of progress or not.

Please fix that thing as it is unbelievably annoying for a feature that is only available on your $450 top of the line watch!