Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Half marathon PR does not sync

8147809
over 4 years ago

Hi,

I am having an issue with my PR. 

I ran a half-marathon yesterday and did PR https://connect.garmin.com/modern/activity/5703179033

However my PR still shows previous time 2:16:59.

Any idea?

Thanks.

  • 0 over 4 years ago

    Ok, I just marked it as PR manually from the Garmin Connect Web app (using the cog wheel). It's a shame that the watch recognizes the PRs but do not synchronize them. I actually PRed on 5k during the last 5k of that run, and there's no way to sync it, while the watch did recognize it. Any clue?

  • 0 over 4 years ago

    First, your activity is private, so no one except you can see it.

    And second, a new PR has to be confirmed by the user in Garmin Connect before it can replace the old PR.

  • 0 over 4 years ago in reply to tmk2

    Thanks a lot.

    So, my activity is for "connections only" like all my activities. Do you mean it should be Public?

  • 0 over 4 years ago in reply to 8147809
    8147809 said:
    Do you mean it should be Public?

    If you post it publicly and wish that we look at it, and try to tell you what's wrong with it, then yes. Otherwise, it is not necessary.

  • 0 over 4 years ago in reply to trux

    BTW, each time you confirm a new record in Garmin Connect, or assign one manually, you have to use the button "Send to device" on that page, so that the PR table is updated on the watch too.

  • 0 over 4 years ago in reply to trux

    Are you sure about that? It might be true for manually assigned PRs, but PRs detected by the watch DO NOT need to be sent back to the watch after confirming in garmin connect. It's been a while since I last broke a PR, so things might have changed, but I never sent any records back to the watch after confirming in Garmin Connect.

  • 0 over 4 years ago in reply to tmk2
    tmk2 said:
    Are you sure about that?

    Not absolutely, but I prefere sending the updated PR table to the watch every time I approve a new record anyway. It costs nothing, and you are on the safer side. I had an issue where a new PR was not recognized in the past, too. It may have been because of another problem, but since I update the table regularly, it did not re-occure. Besides that, I had to do couple of hard resets lately, and refreshing the PR table is necessary in such case too.