Threshold pace incorrect

A few days ago I forgot to stop my watch after a run and drove away in my car with the timer still running. I was able to use the trim activity function in Garmin Connect to delete the last few miles of the run/drive and the data largely corrected itself. However, I see it triggered a massive change in my Threshold Pace (but not threshold heart rate) and trimming the data doesn't seem to have corrected it. This metric seems to have a strong influence on the paces for the Daily Suggested Workouts which I have been following in the run-up to a marathon. The workout suggestions are no longer aligned with my abilities and I am wondering if t here is any way to force the watch to recalculate the threshold pace value or stop the watch from using the now deleted data and messing up the calculation. 

  • there is no way to modify the LTHR pace, the only way is to know it by yourself doing field tests, or by let it enabled and it will recalibrating each run, try to use chest strap to get best values, more indeed if the training is threshold of vo2max

  • Thank you. That was my reluctant conclusion too. It seems odd that the threshold pace will use data which has been entirely deleted from the system - particularly when you can manually correct your threshold heart rate. Unfortunately my threshold values update only once in a blue moon over the past year and it looks like the DSWs are going to be unusable for the foreseeable future. It is a bit demoralising to be presented with a 0% execution score at the end of every run!

  • i dont rely in this features since many months, so dont care about score execution, care about metrics, follow your real LTHR and LTPace when the DSW tell you to do threshold workouts, and for base runs the same, do at your pace, this is whats more important

  • I spoke to Garmin yesterday who were adamant that if I delete the activity with the incorrect data and do another run, the threshold data will overwrite. They say trimming the activity leaves the data intact and just changes how it is presented on Connect. We shall see…

  • For what it is worth, Garmin support was incorrect and, as you suggested, once the data is in the calculation it cannot be removed even if the offending activity is deleted. 

    It seems inevitable that there will be circumstances, including as in this case user error,  in which false data is used to calculate the Running Lactate Threshold Pace and it seems to be an oversight that there is no way to correct it.

  • yes, this is why i finally opted to disable the feature, and i do field test regularly and i take this data into account, because the threshold feature was giving last months unreal and very far metrics

  • A few days ago I forgot to stop my watch after a run and drove away in my car with the timer still running. I was able to use the trim activity function in Garmin Connect to delete the last few miles of the run/drive and the data largely corrected itself. However, I see it triggered a massive change in my Threshold Pace (but not threshold heart rate) and trimming the data doesn't seem to have corrected it. This metric seems to have a strong influence on the paces for the Daily Suggested Workouts which I have been following in the run-up to a marathon. The workout suggestions are no longer aligned with my abilities and I am wondering if t here is any way to force the watch to recalculate the threshold pace value or stop the watch from using the now deleted data and messing up the calculation. 

    Did you accept the new data? When there is a change in THP/THHR and/or THpower the watch asks to confirm/accept (idem when a new HRMax is detected (when enabled). Probably too late now but this avoids corrupt data.

  • I wasn’t aware of doing so. I thought I pressed the lap/back button, but perhaps not.

  • i cancel a few times the new values and the watch registered over my decision, in my last forerunner i did few times and worked, but in the epix nop,