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

Express keeps uploading (some) old activities despite cleared history

Former Member over 10 years ago

I use Garmin Express together with my Forerunner 305 on a Macbook Pro (OS X 10.9.4). Unfortunately whenever I connect my watch Express uploads a couple of old activities that are already in Garmin Connect leading to duplication. To aggravate the issue this continues to happen after I cleared the history on the FR305. I have already removed my device from my account and reconnected it, did a complete reset of the FR305 and trashed and reinstalled Garmin Express. So far to no avail. Not only do I have to clear out duplicate activities after every sync, the sync operation also takes a long time.

Below is part of the log for my last sync which let to a duplication of a run on August 10th (see picture).

2014-08-14 15.27.51 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-06-17-154547.TCX) already exists (409), skipping
2014-08-14 15.27.51 (GMT+02:00) | 2055 | I | The file[2014-06-17-154547.TCX] was processed succesfully with code: 409
2014-08-14 15.27.53 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-06-21-144346.TCX) already exists (409), skipping
2014-08-14 15.27.53 (GMT+02:00) | 2055 | I | The file[2014-06-21-144346.TCX] was processed succesfully with code: 409
2014-08-14 15.27.59 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-06-22-143845.TCX) already exists (409), skipping
2014-08-14 15.27.59 (GMT+02:00) | 2055 | I | The file[2014-06-22-143845.TCX] was processed succesfully with code: 409
2014-08-14 15.28.02 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-06-24-143448.TCX) already exists (409), skipping
2014-08-14 15.28.02 (GMT+02:00) | 2055 | I | The file[2014-06-24-143448.TCX] was processed succesfully with code: 409
2014-08-14 15.28.06 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-06-26-150811.TCX) already exists (409), skipping
2014-08-14 15.28.06 (GMT+02:00) | 2055 | I | The file[2014-06-26-150811.TCX] was processed succesfully with code: 409
2014-08-14 15.28.11 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-06-30-182446.TCX) already exists (409), skipping
2014-08-14 15.28.11 (GMT+02:00) | 2055 | I | The file[2014-06-30-182446.TCX] was processed succesfully with code: 409
2014-08-14 15.28.12 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-01-154312.TCX) already exists (409), skipping
2014-08-14 15.28.12 (GMT+02:00) | 2055 | I | The file[2014-07-01-154312.TCX] was processed succesfully with code: 409
2014-08-14 15.28.20 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-05-123203.TCX) already exists (409), skipping
2014-08-14 15.28.20 (GMT+02:00) | 2055 | I | The file[2014-07-05-123203.TCX] was processed succesfully with code: 409
2014-08-14 15.28.26 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-10-172925.TCX) already exists (409), skipping
2014-08-14 15.28.26 (GMT+02:00) | 2055 | I | The file[2014-07-10-172925.TCX] was processed succesfully with code: 409
2014-08-14 15.28.34 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-13-143652.TCX) already exists (409), skipping
2014-08-14 15.28.34 (GMT+02:00) | 2055 | I | The file[2014-07-13-143652.TCX] was processed succesfully with code: 409
2014-08-14 15.28.39 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-16-171008.TCX) already exists (409), skipping
2014-08-14 15.28.39 (GMT+02:00) | 2055 | I | The file[2014-07-16-171008.TCX] was processed succesfully with code: 409
2014-08-14 15.28.46 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-17-152004.TCX) already exists (409), skipping
2014-08-14 15.28.46 (GMT+02:00) | 2055 | I | The file[2014-07-17-152004.TCX] was processed succesfully with code: 409
2014-08-14 15.28.54 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-20-133427.TCX) already exists (409), skipping
2014-08-14 15.28.54 (GMT+02:00) | 2055 | I | The file[2014-07-20-133427.TCX] was processed succesfully with code: 409
2014-08-14 15.29.00 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-22-164841.TCX) already exists (409), skipping
2014-08-14 15.29.00 (GMT+02:00) | 2055 | I | The file[2014-07-22-164841.TCX] was processed succesfully with code: 409
2014-08-14 15.29.02 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-26-144250.TCX) already exists (409), skipping
2014-08-14 15.29.02 (GMT+02:00) | 2055 | I | The file[2014-07-26-144250.TCX] was processed succesfully with code: 409
2014-08-14 15.29.17 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-27-164300.TCX) already exists (409), skipping
2014-08-14 15.29.17 (GMT+02:00) | 2055 | I | The file[2014-07-27-164300.TCX] was processed succesfully with code: 409
2014-08-14 15.29.21 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-29-184711.TCX) already exists (409), skipping
2014-08-14 15.29.21 (GMT+02:00) | 2055 | I | The file[2014-07-29-184711.TCX] was processed succesfully with code: 409
2014-08-14 15.29.31 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-30-115306.TCX) already exists (202), skipping
2014-08-14 15.29.31 (GMT+02:00) | 2055 | I | The file[2014-07-30-115306.TCX] was processed succesfully with code: 201
2014-08-14 15.29.33 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-07-30-122915.TCX) already exists (409), skipping
2014-08-14 15.29.33 (GMT+02:00) | 2055 | I | The file[2014-07-30-122915.TCX] was processed succesfully with code: 409
2014-08-14 15.29.38 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-08-01-170501.TCX) already exists (409), skipping
2014-08-14 15.29.38 (GMT+02:00) | 2055 | I | The file[2014-08-01-170501.TCX] was processed succesfully with code: 409
2014-08-14 15.29.51 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-08-03-081902.TCX) already exists (409), skipping
2014-08-14 15.29.51 (GMT+02:00) | 2055 | I | The file[2014-08-03-081902.TCX] was processed succesfully with code: 409
2014-08-14 15.29.55 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-08-05-072638.TCX) already exists (409), skipping
2014-08-14 15.29.55 (GMT+02:00) | 2055 | I | The file[2014-08-05-072638.TCX] was processed succesfully with code: 409
2014-08-14 15.30.05 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-08-07-175247.TCX) already exists (409), skipping
2014-08-14 15.30.05 (GMT+02:00) | 2055 | I | The file[2014-08-07-175247.TCX] was processed succesfully with code: 409
2014-08-14 15.30.07 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-08-10-150128.TCX) already exists (409), skipping
2014-08-14 15.30.07 (GMT+02:00) | 2055 | I | The file[2014-08-10-150128.TCX] was processed succesfully with code: 409
2014-08-14 15.30.09 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-08-10-152216.TCX) already exists (202), skipping
2014-08-14 15.30.09 (GMT+02:00) | 2055 | I | The file[2014-08-10-152216.TCX] was processed succesfully with code: 201
2014-08-14 15.30.21 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-08-10-154316.TCX) already exists (409), skipping
2014-08-14 15.30.21 (GMT+02:00) | 2055 | I | The file[2014-08-10-154316.TCX] was processed succesfully with code: 409
2014-08-14 15.30.22 (GMT+02:00) | 2055 | I | Update Check started for device 3825432902
2014-08-14 15.30.22 (GMT+02:00) | 72087 | I | Update Check Complete: [Update Group for device 3825432902 - MU:0, MR:0, MS:0, CU:0, RF:0, OF:0, LP:0, SR:0]
2014-08-14 15.30.22 (GMT+02:00) | 77451 | I | Cleaned map cache of 0 item(s).
2014-08-14 15.30.26 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-08-12-171846.TCX) already exists (409), skipping
2014-08-14 15.30.26 (GMT+02:00) | 2055 | I | The file[2014-08-12-171846.TCX] was processed succesfully with code: 409
2014-08-14 15.30.34 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Upload file (2014-08-13-164418.TCX) already exists (409), skipping
2014-08-14 15.30.34 (GMT+02:00) | 2055 | I | The file[2014-08-13-164418.TCX] was processed succesfully with code: 409
2014-08-14 15.30.34 (GMT+02:00) | 2055 | I | Device [3825432902] update with reason: 13
2014-08-14 15.30.34 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Changed to [Succeeded] phase.
2014-08-14 15.30.34 (GMT+02:00) | 2055 | I | [SyncUpload-3825432902] Released sleep lock
2014-08-14 15.30.34 (GMT+02:00) | 2055 | I | Successfully sent sync analytics report
2014-08-14 15.30.38 (GMT+02:00) | 2055 | I | Getting authenticated connect URL for device 3825432902

0 EXPRESSCUSTOMERCARE over 10 years ago

It looks like we might need to perform a master reset on the device:
http://support.garmin.com/support/searchSupport/simpleCase.htm?caseId={4315c510-5161-11dc-4ec8-000000000000}&kbName=garmin

Albert

0 Former Member over 10 years ago

Hi Albert,

thanks for the reply. Unfortunately your link leads to a error page ("HTTP Status 500 - The server encountered an internal error () that prevented it from fulfilling this request.")
I have already tried doing a Hard Reset (Power off, hold down power and mode button) twice without any success. While it does delete my user settings and it claims no History is available, Garmin Express still pulls the data from the device and uploads it to Garmin Connect. After every sync there are now about 5 duplicate activities that I have to delete again and again.

0 Former Member over 10 years ago

I have the same problem.
The link provided is give as 404 Error and the hard reset doesn't change anything.

Even with the rest there ares still more than 100 activities being synced by Connect Express despite the fact that I have no history left on my watch.

I looked in the Classical Mode website, to see what it says about the content of my watch in terms of activities.
It turns out that in Classical Mode, it appears that all my activities are still available to upload from the watch --- the hard reset doesn't seem to clear the history as it claims.

Using the Modern Mode Website, I and the Connect Express interface, I still can't sync Workouts to my watch.

TEMPORARY SOLUTION I FOUND ---
I tried uploading the workouts from the classical mode and it worked as a charm.
While it is a relief I can upload the workouts in this way, it's way to many hoops to jump through as compared to the old way.
Very disappointing update of the website and uploading tool since instead of being flawless and easier than before, it's giving me headaches and taking forever every time I want to upload my activities.

0 EXPRESSCUSTOMERCARE over 10 years ago

You may need to enable the feature in Express to erase the activities from the device after a successful upload. I don't recommend keeping the settings enabled but it will probably clear up your current issue.

Open Garmin Express
Click Device
Scroll down to the Garmin Connect Account section
Check Erase data on this device after successfully syncing
Sync the watch again

Disable the setting then create a test activity and sync. The duplicates should be gone.

Curt

0 Former Member over 10 years ago

Curt,

Thanks for the suggestion but I'm afraid to do as you mention because now, any way I try to sync my activities (runs I did since my last post) they don't upload to Garmin Connect anymore.

It says on both my watch and the Connect Express Mac App on my laptop that they have synced but that's not the case because they don't show up in my activities. I'm afraid that if I tell it to delete the activities after syncing they will just be deleted.

Seriously, this is getting really frustrating. Every time I try to sync activities now it's a 30 mins ordeal and I don't even get to sync them anymore. What's the point of actually even owning a Garmin watch if I can't even use it properly.

You guys offer solutions but they aren't really solutions to the actual problem out there you are just telling us to trouble shoot on our end, risking loosing our data.

Please let me know how I can go back to the way this was before. It's wasn't perfect but at least it work.
I HATE THE NEW GARMIN CONNECT APP AND WEBSITE.

0 arcleve over 10 years ago

I'm having this same problem with a ForeRunner 305 my girlfriend has and the Garmin Express app on our MacBook Air. I've tried deleting all of the user history, checking the delete after upload box in Express, performing a hard reset, and deleting and re-adding the device to her Garmin Connect account. It still lists ~100 activities every time I plug it in and takes over 15 minutes to sync (including re-uploading blank activities that have previously been deleted from Garmin Connect.

The incredibly odd thing is that all of the user data has been deleted from the device, and it's been through a hard reset - so where is the data being stored that it can be re-uploaded to Connect? Is there some sort of cache that should be cleared on the Mac we're using to upload the data?

Any thoughts would be greatly appreciated.

0 SUSSAMB over 10 years ago

Probably you haven't emptied the trash?

0 EXPRESSCUSTOMERCARE over 10 years ago

Use the suggestions in post #5 and once the sync is complete, Express will not try to pull all the activities on when you sync in the future.

Curt