Related

Activity Personal Best

Tommisole
29 days ago

Ater every charge the watch reset the PBs. So no matter the real times, every new activity (swim, bike or run) after a new charge is a PB. Even if only a recovery session.

  • 0 29 days ago

    Do you accept the PB-s? If not then it makes sense.

  • 0 29 days ago in reply to flocsy🤠
    flocsy🤠 said:
    Do you accept the PB-s? If not then it makes sense.

    That's the way it works, but I disagree that it makes sense. Whenever this comes up, people say that no matter time they run (whether it's faster or slower than the previous attempt at the same distance), they get a PB.

    Based on the support article linked above, it seems that you only have to accept a PB for any given distance once (in Connect), then further PBs will work as expected without any intervention. (I would argue that the explanation in the support article isn't crystal clear though.)

    To me this seems extremely unintuitive.

    - If the argument is that this system is in place to avoid bogus PBs, I would argue that bogus PBs can still happen with the existing system.

    - Why require the user to accept a PB once but not subsequently? Wouldn't it be more consistent to either not require any PBs to be accepted or to require all PBs to be accepted? If you need to accept a PB for a given distance once in order to establish it's a real PB, why not have the same requirement for subsequent PBs at the same distance?

    - Why require the user to use Connect to accept a PB that's displayed on the watch (two completely different places)? If the user must accept a PB, why not allow them to accept it on the watch (after the activity, of course)? Isn't this the kind of functionality that should work without any interaction with Connect (like HR monitoring, stress, body battery, sleep/nap detection, step counting, floor counting, VO2 Max estimation, etc., etc.)?

    I think the best argument that this doesn't make sense is that it comes up as a question all the time, and it's addressed in the support article linked above. If it made sense, it would be more or less self-explanatory.

    Receiving a Personal Record From Garmin Connect:

    If a new personal record is detected, you will be presented with an option to accept or reject the activity as a PR. You can also edit, select, or delete personal records in your Garmin Connect account. For steps on how to do this, see below.

    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.

    Yeah, the reason it's a note is that it's something that requires special attention or explanation - i.e. it's not intuitive.

  • 0 29 days ago in reply to FlowState

    Anyway, I'll just say that Strava assigns PBs without user intervention. If you feel you got a PB in error, you can flag your own activity (although this doesn't seem to work for every part of the UI that displays best efforts.)

    For Garmin, I think it would make more sense to:

    - give users a chance to reject a PB (but to accept PBs by default)

    - to put the UI for accepting/rejecting a PB in the same place as the UI that displays the PB. (i.e. PBs displayed on the watch should be accepted/rejected on the watch, if they must be accepted or rejected.)

  • 0 29 days ago in reply to FlowState

    Yeah, it would make sense to have a way to accept PB from the watch, similar to lactate threshold, max hr