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

I have tried connecting it to an iPhone instead of an Android - still, no luck!

I had this issue for a long time but it resolved for me almost two months ago. I have ~6 autodetected LTHR updates since then that show up in Connect. FR955, HRM Pro+, iPhone 15. 

When it wasn’t working I used a workaround that someone else on the forums shared: instead of syncing the run via Bluetooth on your phone, sync over wifi directly from the watch. 

I would suggest turning your phone off altogether before going on a run lest your watch sync with it automatically in the background before you can manually sync over wifi directly from the watch. 

From the watch:

• hold the Up button
• scroll down to Connectivity and select it
• scroll down to Wi-Fi and select it
• scroll down to Wi-Fi Sync and select it

See if that helps get the LTHR updates from your watch to Connect after your next run  

(LTHR syncing started working for me again around the time I switched from an iPhone 8 to an iPhone 15. Not sure if that’s connected or just a coincidence.)

RockBastard said:

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

Ok, recently my FR 955 also said „Manual Entry“.
But I have to say, I had some illness in November and started with lower intensity training. So there really was no update for lactate threshold to detect.

Today I integrated three intense sections into my run, pulse was in the 170s for minutes, so clearly above my threshold of 165.

I got an update for my threshold on the watch (to 167) and confirmed. It was synced to Connect without problems.

So my first question is: Did you have intense trainings recently that would update lactate threshold?

Second question: Has your watch given you an update after a run? (New values for threshold that you needed to confirm)

I’ve only had LTHR updates after runs with harder/faster components, never on easy runs. 

When my watch auto-detects a new LTHR then it gives me the option of accepting the new LTHR after saving the run but before displaying the results of the run. 

Thanks!
To the first, that's a yes. I have done quite a few intense runs, so much so that my VO2 max has climbed from 52 to 54. Furthermore, I can see that in my daily suggestions, the pace has also been lowered by 5-sec per Km.

Secondly, no. I used to get these notifications on my 945 LTE. I haven't seen any on my 955 and also on my 945 LTE if there weren't any updates, I would still have a flat curve on Garmin Connect as per the picture here:

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. 

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

Updates on LTH should go both ways, up and down. The way you described it it is bound to only update when going up.

I used to get a reading on GC no matter whether it was going up or down and had a blue and red curve. I could follow up on it.

I can't, however, find anywhere where I describe it as a thing that only works when it goes up, hence the word "update." 

Hello my Threshold never change since long time. It is related to the fact I am not using the chest band but only the watch? I am set on automatic threshold but anyway never change