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

Is there a problem with the Garmin Connect backend?

I just got back from a run and synced my Forerunner 620 via WiFi. The transfer completed, but when I logged into Garmin Connect, the activity wasn't there. I synced again with the USB cradle, and the activity still did not appear in Connect. I just now tried uploading the FIT file manually, and Connect is hanging on Uploading...

I also tried transferring my personal records to the 620, on which I did a master reset last week after the watch rebooted at the end of a workout. Connect opened Garmin Express to do the transfer but it hung while preparing the file, and the file modification date did not change on the watch filesystem, so it had not yet reached the point of writing data to the watch.

Makes me wonder whether part of the site's back end has crashed. Has anyone else noticed this problem?
  • Former Member
    0 Former Member over 10 years ago
    Same problem here today, with both a Forerunner 220 (USB cable) and a Garmin Swim (ANT+ connection). Very frustrating.

    Clicking the "View Errors" button in Garmin Express is useless -- it just gives the message "Sorry, we could sync your device. Please try again."

    Just this morning I was lamenting to a friend about how expensive these Garmin devices are, and how glitchy the devices and Garmin web services tend to be...
  • Former Member
    0 Former Member over 10 years ago
    I have the same issue (I use Garmin Edge 800). From the sounds if it, it's not on the end user or our devices...rather seems to be w/ Garmin Connect itself. I've skipped my stretching and my protein after my ride while spending so much time trying to get my activities today uploaded. The least Garmin could do is post a notice on the homepage of our Garmin Connect dashboard so I wouldn't have wasted so much troubleshooting time.
  • Former Member
    0 Former Member over 10 years ago
    Same problem here with my 210. I had a to get a new charging cable (puppy chewed the original one...) and was worried that was causing the issue, but apparently everyone is having trouble uploading to Garmin Connect today.
  • Ditto with all of the above -- file won't upload automatically or manually -- from an FR 620. And the website will not allow me to add it manually -- the same "value not accepted by database" error as noted above. And the file is not corrupted as the site suggests -- because I was able to upload it to Strava.

    Hello, . . . Garmin . . . ? Anybody home?
  • Former Member
    0 Former Member over 10 years ago
    Same Here. 910XT. Synced 4 different runs yesterday, no problem. Tonight's run will not sync, cannot manually upload the information either. Ugh!
  • Former Member
    0 Former Member over 10 years ago
    Same problem with FR610 and Edge 500 - Garmin express says "Sync complete" but nothing is there.

    Been doing it since saturday 23rd.
  • Former Member
    0 Former Member over 10 years ago
    Same problem with my Garmin Forerunner 220. Any response from Garmin on this yet?
  • Former Member
    0 Former Member over 10 years ago
    Ditto here with a Forerunner 10. When using Garmin Express, it tries for a few seconds, the progress bar completes half way and then fails with a generic error. Attempts to upload through the 'classic' uploader also fail (the process indicator just spins and nothing happens). I am able to upload runs to Mapmyrun.com, so it's most likely not a problem with he watch or the the gpx data.

    Also, I'd really appreciate it if Garmin could be semi-proactive and post a notice in the forums/connect or on the twitter feed letting us know that they're looking into it.
  • Former Member
    0 Former Member over 10 years ago
    I'm in the same boat with the forerunner 410. It really is starting to be a pain
  • Same boat with my 610. Both in terms of uploading from my watch, manual upload from a GPX file, and creating a manual activity. Nothing works. Lame.