Records recorded wrong

Former Member
Former Member

Hi,

I was wondering if anyone else had this problem in the past (search didn't find anything).

I went for a morning run today, after i finished the watch told me that i had set 3 new records (fastest mile, fastest 1k and fastest 5k - 34:00min).

The weird thing is that last week i actually set a new times for these records (5.01km - 32:54min, during that run i also had a faster 1k and faster mile).

The last time i checked the records saved on the watch were accurate (pointing to the time of 32:54min for 5k etc.

Does the watch remove records after a while, or overwrite them?

It's not a very crucial feature, however it seems like such a basic thing that you would expect it to work.

Regards,

Laurens

  • Former Member
    0 Former Member over 5 years ago

      Attached also the screenshots. Both workouts are actually recorded j. The same week which would lead to believe that it should be easy to compare for the instinct/garmin connect

  • Does the watch remove records after a while

    No.

    or overwrite them?

    It might, if you send old records from Garmin Connect to the watch.

  • Does the watch remove records after a while, or overwrite them?

    Normally, you have to approve any new record. I do it in Garmin Connect Web. I do not have any new pending record right now, so cannot check whether it possible approving pending records also directly on the watch, or on the phone app. But if you did not confirm the previous record anywhere, then it was overwritten by the new one.

  • Former Member
    0 Former Member over 5 years ago in reply to trux

    Thanks, I've just checked and my time from 24/04 (34:30) was listed in Garmin Connect Web + in Connect app. It was suggested that today's run (34:00) should be set as new record with a button to accept it, or keep the old one.

    Doesn't really explain why my faster time from 22/04 is not in there. Maybe it got deleted bcs i never actively accept it (had no idea that you could accept/reject).

    Let's assume going forward it will track it correctly!

    Tnx,