You would think that the programmers at Garmin would be able to figure out how to prevent this problem by now! Not the brightest bulbs on the tree, I guess.
Usually, rebooting the Garmin Connect servers fixes this problem. Can someone send a not to HQ to do the reboot please?