Personal record for Marathon distance incorrect

I don't run these long distances very often. Today was only my 2nd Marathon. After the first one a couple of month back I already noticed there was something wrong with the record displayed on Garmin connect. So today I made sure I really got the full distance and during the run I never paused the activity and ran from start to finish. Well here is the record shown on Connect.

As you can see it doesn't use the Marathon distance (42.2 km) for the record but instead the time for the longest distance. I remember I got the popup on the watch after the run and it said something like best Marathon with three hours and forty something minutes.

So I analyzed the fit file on Golden Cheetah and the personal record for the marathon should be 3:47:25. BTW all the other personal records are correct. This issue only seems to occur for Marathon distances.

Have any of you experienced the same bug? Where should I report this, so Garmin can have a look into it.

It seems like every time you run a distance longer than a Marathon, the connect software doesn't extract the fastest "Marathon interval".

0 Stelios over 4 years ago

Seems like this happens to people using Stryd.

As for my records ..they have not been updated since i started running with Stryd (about 1 year now)

0 Bernd over 4 years ago in reply to Stelios

Intersting. I also use Stryd. However today I got a new PB for the 1km distance.

0 Stelios over 4 years ago in reply to Bernd

Are you using a Fenix 6 watch ? I found some reports with other watches (From Fenix 3 up to forerunner 245) mentioning that the PBs are not updated

Also, Which datafields ? Stryd zones?

0 Bernd over 4 years ago in reply to Stelios

Yes got a F6pro. I only use Stryd zones. Pace and distance are set to always. My PB's get updated. No problem with any of the distances except the Marathon one

0 rimmer_9178 over 4 years ago

I had this today. Really annoyed me. I ran 26.32 and total time was 4:00:27. Fastest marathon on Garmin is now 4:00:27 when I actually hit marathon at 3:59:26 which I witnessed at 26.2 and on strava. This implies it took me 0 seconds to run 0.12 miles. Such a bad failure. You cant say 0.1 miles is outside of tolerance.

0 tmk2 over 4 years ago in reply to rimmer_9178

Please read this:

https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-645-645-m/242325/5k-personal-records-being-recorded-incorreclty

0 rimmer_9178 over 4 years ago in reply to tmk2

Well there you go. Should be an option to choose as this might be ok for races but no good if like me you’re running a marathon circular from your front door. I’ll read more and work out the tolerance so I ensure I run further.

0 mcbadger over 4 years ago in reply to rimmer_9178

If you want to get exactly marathon distance according to your watch, probably best to create a 26.22 mile workout in Connect, send that to your watch, and hit stop as soon as it alerts.

That said:

rimmer_9178 said:
This implies it took me 0 seconds to run 0.12 miles. Such a bad failure. You cant say 0.1 miles is outside of tolerance.

Marathon distance is 26.22 miles, not 26.2. So the difference is 0.1, not 0.12 miles, which is less than 0.4 % difference. Gps and foot pods are nowhere near that precise, you’ll be doing well to get as close as 1%; the Jones counter system they use for official route measurements still include a short course prevention factor of 0.1%. 0.1 miles is most definitely inside tolerance for gps over marathon distance. It really, really, isn’t a “bad failure”.

I ran an officially measured half marathon in March and the watch was out by 0.04 miles. Short. Your time over an officially measured course might actually have been less than what your watch was saying at 26.22.

0 rimmer_9178 over 4 years ago in reply to mcbadger

mcbadger said:
It really, really, isn’t a “bad failure”.

I would say it is. It should use 26.22 as the distance it uses to create the personal record or give me an option, such as flagging it as a race, to use the stop time.

0 Bernd over 4 years ago in reply to rimmer_9178

I totally agree. FYI I did another test and ran 45.02km. After that I got the correct record. So you should at least run an additional 800m (maybe Garmins threshold is half a mile?) to get it right. It kind of sucks but at least that's kind of a workaround.