Why is does the 965 think every run is run my longest/fastest run?

Almost every time I finish a run, my Forerunner 965 tells me that it's my longest run or has my fastest mile or fastest 5k or something to that effect when that clearly is NOT true.  Just last weekend I raced a 5 miler.  The next day I did a very slow run and it told me I had done my fastest every mile even though the race (that was still in my history) said otherwise.

  • Maybe it's because records must be confirmed on Garmin Connect (app or web), so if you've never done that everything is a record until confirmed? I don't recall exactly where but have a look and see if you can find it...

  • So I have to manually "confirm" my own records on Garmin Connect?  Really?  Well that's new -- or at least new to me.  The older garmins just used to keep a running tally

  • I think so but I could be wrong… In the app the records are under your profile and then statistics

  • I don't see anything to that effect under my profile on the website.  When I look at the phone app, there are only 4 or 5 different records under running and they only have to do with "steps".  Nothing like longest run or fastest mile. 

  • Actually I found the section on the website and I did find a "fastest mile".  There it says my fastest mile is 1 second.  Seriously, 1 second.  So clearly some bad GPS data went into that.  But if the website thinks that is my fastest mile, then it still makes no sense that the watch thought a 7:40 mile was a new fastest

  • Just a second here. Mine has been doing this too lately. Not every single run, but often I'll get fastest mile awards after a slow jog.

    I don't think users are required to manual input our PRs, that doesn't make sense, it is some cache or sync bug most likely.  If you figure it out write back please.

  • I've been having this same issue lately (past couple of months). Several runs (even easy pace) will say "Fastest 1k". I've just checked my personal records (1k and 1 mile were hidden) at https://connect.garmin.com/modern/personal-records

    1k had a time of 38s (pending), yet the stored record on my Forerunner was more realistic. Have deleted the pending one and re-synced from GC web > Send to Device. 

    Still doesn't make sense, but will report back if I find anything else. 

  • Maybe it's because records must be confirmed on Garmin Connect
    So I have to manually "confirm" my own records on Garmin Connect?  Really?  Well that's new -- or at least new to me.  The older garmins just used to keep a running tally

    Yeah it's super unintuitive and user-unfriendly imo, but I think that's how the newer watches work.

    Garmin obviously recognizes it's confusing so they added a note to the relevant support article:

    https://support.garmin.com/en-CA/?faq=unLSr8lk0z5EUCi0k8Yys8 

    NOTE: If you have not accepted a PR in Garmin Connect or if the particular PR is hidden, your device will continue to notify you of new PRs until one is accepted. To resolve this, you would need to make the PR visible and either accept or reject the automatically detected PR activity. If you know of a PR activity, you can also assign it manually. Once you have accepted or assigned the PR, that information syncs to your device so it can accurately notify you when a new PR has been achieved. 

    The text is also kind of unclear imo, but it does align with everyone's experience that you have to accept a PR (of a given type/distance) in Connect once, otherwise your device will keep acting like you set a new PR (for that type/distance) with every run, regardless of how fast you went.

    I suppose it makes a certain kind of sense: if you have no PR (for let's say 5k) in Connect, then it's almost as if Garmin assumes that your PR for 5k is unspecified (effectively making your PR time infinite) , which means that every 5k run is better than your "PR".

    I don't understand why Garmin wouldn't just automatically accept your PRs as detected by the watch as they did in the past tho. I'm gonna guess there was some issue with bad PRs being automatically detected in the past, and this is their solution (which doesn't seem to solve the problem of bad PRs being auto-accepted *after* you accept a PR for a given distance once).