PR not updating when uploading better PR activity

Sometimes you have to set the PR manually by going to the activity, clicking the cog wheel in upper right corner and select "Set as PR". After you have done that the first time the PR should work and you should just have to accept the new PR in the PR page.

... what e7andy wrote, and additionally you have to send the updated PR table back to the device, each time you adjust it, or approve new PRs. It is the device that does the PR recognition, hence it needs to have the updated PR table.

Hi Andy,

Unfortunately that doesn't work. I can set the whole activity as PR for 40K, which will then calculate whatever fantasy times to display, but after I would upload a better activity, it doesn't take it into account and does not provide a new record to accept. It simply doesn't get it... I had tried it already, but tried it again. I deleted the better one, set the older one as PR, uploaded again the better one, nothing new to accept...

By the way, amazing job you do with the Badge Database, that is absolutely fantastic!

Denser said:

but after I would upload a better activity,

Not sure what you mean by uploading here, but PRs are handled by the device, not in the Garmin Connect account, so only records in activities recorded directly by the device can be recognized automatically. The auto-detection won't work on uploaded, imported, or manually created activites.

Hi Trux,

Here I have to disagree. I am using Zwift, and I am merging the fit file from Zwift with the fit file from my Fenix. I delete the indoor activity from the Fenix and then reimport it as the merged file, so I have the real trace and km from Zwift.

I am sure it works because I have my elevation record as well as my max Watt record from my two imports. The same should happen with the 40K as I would import a merged Fenix/Zwift of 50K with a better 40K PR, so it should be taking it into account the same way than the others...

Not sure how it works for the power and elevation records, perhaps Zwift sends them through the export file in the right format while not doing it for the distance based records. However, normally, records are processed by the device, not by the app or on the server, so unless the record comes from the device (or directly from Zwift), it won't appear on the list of PRs.

Also have a look at the support document How Are Running and Cycling Personal Records Determined on a Garmin Device?. It states the follwoing:

• Activity is required to be recorded using either a running or cycling profile on the device.

The thing is, it comes from the Fenix. I combine the Zwift fit file with the Fenix fit file of the activity I recorded at the same time. So in fact, what I manually import to Garmin Connect is an original Fenix fit file, only including the GPS Information. 

Zwift itself doesn't communicate anything to Garmin Connect that way. All the other records were detected after the upload, I could simply accept the new record.

So simply right now I can't get this one to update...

If the GPS info comes from Zwift, the distance cannot come from Fenix, hence no record will be detected automatically. You have to set it up manually, or do a true outdoor bike Activity with your Fenix.

It's a combined fit file: in the fenix fit file I import the GPS data from the zwift fit file. In the end, what I have is a "fixed" fenix fit file including GPS information. That's how the record for Power or Elevation are detected. The activities I have for these records or from fixed fenix fit files. That's also how GC has detected and awarded me the 40K in 1H Badge. It can detect that, but not show it as a PR. 

For the elevation, it detected immediately the proper elevation (first the Alpe then got updated with Mt Ventoux (Ven-top) which is higher than the Alpe) and awarded the proper corresponding Badge.

So it should detect automatically, as the principle is identical :/

Maybe also my activity is exceeding too much the 40K distance? Could that have an impact on the detection? If yes, it's difficult to understand how the running distances can be detected out of long runs, for example. My better activity is a 49K that includes a faster 40K than my previous 40K record activity...