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

Forerunner 410 - activity on watch, can't upload manually, no file for that date

I have a Forerunner 410. I updated to Garmin Express about 1 month ago. It's been quirky at uploading, but even when it has errors, it usually fixes itself or I can manually upload an activity.

This time, it had an error loading the activity on 7/19 (yesterday). I had a new activity today (7/20) and it uploaded automatically. The 7/19 activity never successfully uploaded.

The activity for 7/19 is still on the watch history. There is no file on my computer for that location (but there are for activities from 6/21 - 7/17, and 7/20).

If I try to go to a manual upload, it shows no activities on the watch (through Garmin Connect).

Can I get my activity from the history of my watch for 7/19 uploaded? I'd like to get my splits/heart rate/running cadence data. I do at least have the overall data and I can look at the splits, but that's not why I bought a Garmin device to do all this manual work. This is my first real issue getting my data, I figured somebody might know how to get it.

Thanks!
  • This can happen if the activity on your device is corrupt. Sometimes a corrupt activity will cause the device to crash/misbehave, sometimes it will not transfer to the computer, sometimes it won't transfer to Garmin Connect. It just depends on the type of error. If you can't get the activity off of your 410, then you're kinda stuck.

    I don't have access to a 410, but if it is anything like the 310XT, 610, or 910XT, you will have a Transfer All option in the History menu. You could try that to get the device to try to transfer the activity again. If that option isn't available, you might be able to remove the device from Garmin Express, rename the folder containing the cached data from your PC (C:\ProgramData\Garmin\GarminConnect\<DeviceId>) and then re-add the device to Garmin Express. That could be enough to convince the device that it needs to upload its data again.
  • Thanks. Apparently it is in limbo to not be retrieved. On a positive note, it's been working correctly since.