Lactate Threshold bug in GC

I've just checked in on the forum to start a thread on this very issue and 'relieved' (well, not really relieved) to see it already reported and that I'm not alone.

My LT has updated a couple of times in the last couple of weeks. The last time I checked it on GC (a few weeks ago - prior to the 2 changes detected by my Fenix3) GC was showing the results fine... Now they are broken. It's as though the units on GC are different to those on the watch - HR is displaying fine, it is the LT pace that's wrong; I wonder if a recent software update has seen GC configured to read minutes/mile for KM/second for example!?

I should emphasise that it is something recent-ish that has caused the issue; all was fine just a few weeks ago for me.

They are also working on a resolution so that all of the erroneous readings are automatically corrected at the same time the fix is released. As long as everything goes according to the current release plan, this fix should be released in early July.

Good news: today's LT reading is correct. Yeah!
Bad news: the old values are still wrong.

@TH3RETIKER,

Thank you for your post.

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.

@TH3RETIKER,

Thank you for your post.

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.

Hi GFM1011 and thanks for the update. I noticed that the graph axes are now fixed but my old LT values are still messed up. Unfortunately I don't have a new LT measurement to verify if it is fixed for me.

[...] the expectation is that any new LT value that is uploaded will be correct. [...]

Confirmed, LT threshold values uploaded this morning are correct again (in graph and value on the right), but previous values are still wrong (GC version 3.8.0.15). The (logarithmic) LT scale spans all these values, the number of horizontal lines has been reduced so that the labeling is readable again.
Thanks for the update! Curious about the announced one that also fixes older values...

Just checked again today 2016/7/18 and the past LT values are still messed up.

Any update on the ETA of the fix?

It is now 2 months and 10 days since I first reported this bug and still our previously recorded VO2Max values are messed up :-(

When can we please have them corrected so that we can see our progress in time?

The initial plan was to have the previous uploads corrected. Unfortunately, there is still not a timeline on when this would be completed.

We do apologize for any inconvenience that this has caused.

I can not confirm.

I have FR630 with current firmware and my pace is always in ultrasonic range with 0.02 in Connect !!!!:mad::mad::mad:
Old values are always wrong.

FR630 display values are corret but not in Connect.

Will be this ever solved?

@Andyt5,

A fix was put in place on July 17 that would correct this issue for any new LT uploads, but there has not been any fixes that would correct previously uploaded data.

If you have an example of a new LT upload after July 17 that is still showing the incorrect value, can you upload a screenshot or the FIT file so that I can get this escalated to the team for further investigation?