how do I set up reports to separate running and cycling
no matter what I change activity name it will all be under running with no cycling activity
thanks dave
Issue with Activity incorrectly classisfied as running
I have a similar issue- when I list my activity correctly as "paddling" the entry becomes changed to "running". Concurrently there is a java error message. This means there was a software programming change that had some errors regarding activity classification, I believe.
There aqre multiple threads on this subject that you can refer to.
The easiest way is to modify the activity immediately after you sync it. Waiting a minute is probably too long.
The other way is to change the activity to cycling, export it, delete it from Connect, and import the changed activity. I do this almost every day since November 15th when the problem started.
Garmin say they are working on fixing it but it's taking a long time.
I've been having the same problem: it ignores all of my walking activities. I haven't tried exporting yet, not quite sure how to do that. What a pain! This seems like a really basic thing.
I use TCX for indoor activities. I haven't had to do an outdoor activity yet but I suppose it would be a gpx file. I would think fit would work which is the Export original option. However the fit file is exported inside a zip file.
To do the export, show the activity on a full page and then click the gear icon in the upper right corner and you'll find the export options.
If you're unsure, I suggest exporting using the various options, delete the activity using the same gear icon. Import each format and see if it suits you. If it doesn't delete it again and try the next one.
One thing to note. When I do an elliptical activity, I choose it as an indoor walking activity. Then I modify it to elliptical, export it and reimport it. When it is first reimported, instead of walking, it says other. So far each time, I have changed the "other" to "elliptical" right after the import and the colour of the bar chart is black as it should be.
Thanks for all the input everyone. Im glad to find that I'm not alone with this issue.
You would think Garmin could repair this in a matter of hours, as there is obviously a coding error from working perfectly before to the crock we have now.
I will wait, and wait, and wait some more for Garmin to fix, and hopefully it can be corrected to be retrospective.
Does anyone have a contact directly with Garmin's technical office where we can rant more loudly?!
The history of this bug goes back to a November 15th planned maintenance shutdown Garmin needed. The shutdown took more than a day when it was supposed to be a few hours. When Connect came back up, this particular function was broken.
Garmin is aware of it and says they're working on it, but more complaining wouldn't hurt. Customer support: U.S.: 913-397-8200
U.S. toll-free: 1-800-800-1020, Canada: 1-866-429-9296.
