Using Samsung S8 running Android 7.0, when I check the Lactate Threshold with Garmin Connect, it does not show any data but it briefly displays "an error has occurred" is this a known bug?
Apologies for this basic question, but has your device detected your Lactate Threshold?
I ask because Lactate Threshold detection is one of the few features that requires a paired chest belt, and can't be measured using only data from the device's integrated optical heartbeat sensor. It also requires heartbeat data from a number of different intensities recorded during the same run, including some time spent running above your LT - which a few folks don't hit in the process of executing their "normal" running routines.
You can always check this for more information.
Of course, if you already knew all that, and your watch has a good LT reading - then well, maybe someone with more knowledge into the Connect app can lend a voice.
Thanks for this info. i did not know there is a dependency on other devices like chest belt. It would be much more user friendly of the connect app would state that instead of "an error has occurred"
It would be much more user friendly of the connect app would state that instead of "an error has occurred"
The error is that there is no LT data available in Garmin Connect for your user account. How you failed to supply data is not for really for the app to conjecture. At best, the app should simply be clearer in the error message to tell the user no data is available, without trying to be helpful in making such data become available.
The requirement for the use of an external heart rate monitor in order to calculate LT metrics is usually stated in the relevant section of a device model's owner's manual. It's the device's job to calculate LTHR and pace (if the model supports the feature) and not Garmin Connect's.
Mine gives me a pace, but bpm is blank on the LT page. I am running with a chest strap and did do the LT test. Now I cannot do it again due to the dangerously cold temps outside.
Can anyone help me with this issue. No matter how many times I manually correct LTHR in the app or web or device (Fenix 5) this never goes away. Do I just need to do a threshold run? is there are a way of getting rid of this erroneous data? Thanks in advance, Vinceciq.forums.garmin.com/.../1293251.jpg
I believe we have the same problem. Mine started at 68 bpm, was going up workout after workout and has stabilized at 135, which is still very low. It doesn't show in the app (instead it shows two dashes), I can only see it on the watch and on the web.
I was running yesterday with a heart rate belt but it does not show me any lactate threshold results. I have Garmin Fenix 6X Pro. What else do I need to do to see results?
