Related
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

Lactate Threshold bug in GC

kalamarios
Hi there. Today my FR630 detected a new Lactate Threshold (7:03/mi 162bpm) but once it got uploaded to GC it shows up as (1:58/mi 162bpm) which screws up the whole plot. Is there a way to remove the measurement without removing the run which is otherwise fine? I am attaching the LT plot as shown at GC to see what I mean:
  • 0
    I have the same problem.


    May i suggest that Garmin moves their software development to the Bay Area so that we can actually start enjoying some solid online services and firmware? Why oh why does it take more than a month to fix a stupid miscalculation of lactate threshold??

    Seriously Garmin?!?
  • Former Member
    0 Former Member
    Well. Once again a proof of the high consideration Garmin have for their customer.
  • Former Member
    0 Former Member
    Mine is still screwed - useless!
  • Former Member
    0 Former Member
    same issue here with LT pace @ 0:07 since april... It was actually worthy paying those extra money for such super LT stats.........
  • Former Member
    0 Former Member
    The Connect team has determined the root cause of this website report error and plan to implement the fix so that the reports display properly moving forward.

    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.

    Thank you all for the discussion and we do apologize for the inconvenience.
  • Former Member
    0 Former Member
    :cool::cool::cool::cool:
  • 0
    The Connect team has determined the root cause of this website report error and plan to implement the fix so that the reports display properly moving forward.

    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.

    Thank you all for the discussion and we do apologize for the inconvenience.


    Hi GFM1011. It's early July :-), any updates?
  • Former Member
    0 Former Member
    Hi GFM1011. It's early July :-), any updates?


    I guess it will be July 2017.
  • 0
    I guess it will be July 2017.


    As long as it is before July 15th, it is considered "early July" :-)

    BTW, I just checked again and it is still messed up ...

    Don't even get me started on the whole RHR fiasco ...