Personal Record View with a BUG. Record time calculations incorrect.

Personal Record View with a BUG. Record time calculations incorrect.

Receiving personal records is bugged.
After a while, I checked the Personal Records section on Garmin Connect Web and noticed that not only is it no longer updated with new performances, but when manually entering them, it doesn't take into account the split with the best record for the selected distance.
For example, in a 13K race with a best 10K record, it enters an incorrect time, entering the total time for the 13K distance and recalculating it as if it were based on a 10K distance.

This calculation is absurd, especially when managing a "record over a distance." Recording such a precise distance is only possible with professional courses and equipment and in contexts like the Olympics or championships, while most users achieve a Personal Best within a longer performance.
This is also described in the guide provided by Garmin.

Other reports suggest entering the time value from the Lap Card for the specific activity in the "record" field.
This is also incorrect because the "record" doesn't necessarily include the distance from the first kilometer. This often happens with longer activities or with uphill sections, and generally in races, it's very rare for the first kilometer to be the fastest.

I've attached two screenshots of the incorrect automatic calculation when setting an activity as a Personal Record, and of the Lap Sheet, where you can see that the 10Km Personal Record is between km 2 and km 11.

An alternative that's not very nice to describe is to use Strava to read the exact time of the Personal Record and report the Strava PR data in the Garmin table. Is this what it's supposed to be?


The 12km activity containing the 10km personal record is in yellow, and the incorrect automatic calculation recalculating the total time of the 13km activity over the 10km distance is in red. Even the average pace is recalculated to add further hilarity to an already ridiculous record-breaking time.


Below is the Lap Sheet of the activity in yellow, where you can clearly see that the "10Km record" interval runs from Km 2 to Km 11. Strava (I'm not attaching the screenshot) calculates it with a time of 46:49 and a pace of 4:41 min/km, which is quite different from Garmin's embarrassing calculation of 1:03:07 with a pace of 6:19 min/km.











  • I must have Connect+ to view this stat correctly?

  • The way Garmin PRs have historically worked is:

    1) If you run close to the PR distance, Garmin uses the entire activity time for the PR (and ofc it uses the entire activity distance to calculate the pace. I think the rationale here is that if you run a race, you will never run the exact distance (either in reality or according to GPS), so it actually makes sense to use the entire activity time here.

    2) If you run much farther than the PR distance, then Garmin uses only the time for the exact PR distance to determine your PR (which is what you would expect, in this case).

    Strava only ever uses the exact time and distance for PRs, which is what people expect. Indeed, most of my Strava "estimated best efforts" are wrong (too fast) for races, because I recorded slightly more distance than the nominal race distance. But Strava does what everyone expects them to do, even if it's wrong.

    I do think Garmin is trying to do the right thing in general (as described above), but it appears wrong to most people because Garmin doesn't really explain it properly (this happens a lot with Garmin imo).

    However, in this specific case where you recorded 13.46 km, it doesn't make sense that Garmin would use the time for the entire 13.46 km to determine the 10k PR. Plus 1:03:07 is obviously longer than your previous PR of 55:37. It also doesn't make sense that the full time for 13.46k (1:03:07) would be used to calculate the PR pace as if you only ran 10k, as you pointed out.

    So this does seem like a bug to me.

    You might want to contact Garmin support: https://support.garmin.com/ or [email protected]