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

BUG- sw 17:26: Lactate Threshold Not Updating in Garmin Connect

I can see that this is somewhat of a persistent problem - Is there a fix for it?

Per my pictures below, I have auto-detection, but my watch believes it is a manual entry, and on Gramin Connect, nothing happens.

Thanks!

Top Replies

RockBastard over 1 year ago in reply to jambongris +4

Hurray - finally! An update on all parameters :-) What triggered it ?- I have no clue, but the graph from GC speaks for itself!

Thanks for all the comments and good suggestions
RockBastard over 1 year ago in reply to 4977680 +2

It did not make any difference to me; It was a one-off. You get one update - that's it.

Before it broke - you could follow and see your updates, like in the picture below - the empty BPM field seems…
jambongris over 1 year ago +1

Went out for a run today: 12 km total with 2x3k at slightly above threshold and got this when saving the run:

Can confirm that it also showed up in Connect.

All Replies

0 4977680 over 1 year ago in reply to RockBastard

you are correct as it is anyway a one time update of LTH and than never update again. I have this problem since Forerunner 945 and now also on 955 so it is an old problem to be addressed

0 G141592653589793238 over 1 year ago in reply to RockBastard

You get this update doing a normal Running activity or performing a LTH test manually? Thanks!

0 RockBastard over 1 year ago in reply to G141592653589793238

Regular running activity, and before it broke, you would get updates (up and down) every time there was a change.

0 G141592653589793238 over 1 year ago in reply to RockBastard

Thank you very much for your response. It has worked fine for me so far, but I want to test to see if it still works that way, that's why I asked you. Thanks!

0 RDW over 1 year ago in reply to 4977680

Yes. It requires a strap.