Suddenly Garmin Connect is not showing me the details (track on map, heigh profile, etc.) for my activities older than ca. 3 months, that is before 18.11.2018 How about you, can you display the older activities as usually?
Starting here with 19th of November 2019, all details including the track on map are gone - but interestingly only for my running and nordic walking activities!? My bike activities from holidays are shown as normal...
Here's a running activity from 22nd of October, and here a bike activity from four days before - no details on the running activity, but all for the bike activity (had no HRS with me while biking)....
At first the disaster with the IQ fields and now this - i hope, Garmin will restore this!
All of the affected activities before 20th of November 2019 are imported from other sources, like Runtastic or komoot, and are not recorded with Garmin units - this should be the reason why our bike activities from holidays in October are already shown completely, as i already have my Edge Explore at this time, but not my Forerunner 645M! The Forerunner was used from 26th of December onward.
But the running/nordic walking activities between 20th of November and 26th of December are also imported from Runtastic and there are all details shown!?!?
Hi Rober, Thanks a lot for your feedback. I also wrote an email to Garmin. In my case the type of activity (running, bike, etc) doesn't matter. For my user for old activities there is only a starting and ending point available so the path on the map is only a line between this to points. I'll let know if I get an answer from Garmin. I am also interested if other users are affected.
I'm also affected, exactly the same issue. I used to own an forerunner 405 and sync it with sporttracks. When I switched to GarminConnect, I exported data from sporttracks as .tcx files (several activities in one file) and imported to GC. Worked perfect. Now, those activities don't show map and graphs any more, however, I can still export my original .tcx files I used to use for import.
Some update: I found it's not related to imported data. It's just all data before (in my case) 8.12.18, from my FR405 (using old tcx format, not fit as the unaffected Edge does). When exporting "original file", then deleting it in GC, an re-importing it, it's okay again. So, since the bug obviously is not related to some "alien" file formats produced by third party exportes, but affects FR405 files directly uploaded to GC in november and before, I am pretty sure Gramin will be able to fix this soon !
I got a reply from support saying that because forerunner405 where the data affected originate from is no longer serviced, they can't make a case for that. If it happens for new products such as FR645, I should let them know. Nevertheless, they will continue to look into this from their side more as well !
For me, this is not a FR405 issue, but a GC issue with TCX, since the data used to be there, and reappear if I export and reimport exactly the same original .tcx file If the data I upload to GC today from my new 645 may vanish when 645 is out of service in a couple of years, Garmin should state that data stored at GC cloud are not in a safe harbour. I would expect data that i uploaded any time in the past succesfully to remain available and to be safe.
So, let's give the experts at Garmin some time, and I hope if there are more complaints, maybe even with data from more recent devices, they may give priority to it. And please, those who also have the issue, please post it here, telling us where the affected data originate from (device, imported), maybe it helps to find a systematic cause. Also, if you have news from Garmin's side, share it with us.
Hi, all my tracks are recorded with Garmin watch 310XT, the older which are not displayed correctly as the newer which are ok. I'm also thinking that this is not an issue of particular watches but rather the availability of the data on the Garmin backend cloud.
I've got such answer from the Garmin support:
"The issue you are referring to is something that we are aware of and are working hard towards a resolution, however, we do not have a time frame for this to be completed as yet. I have added you to the relevant case so that you can be notified once the issue has been resolved."
As for me, only imported data (from Runtastic and komoot) before 19th of November is affected - synced them with 'SyncMyTrack' (android app) and all data from my running and walking activities from the last five years where synced successfully with all data (like heartrate, pace, laps, and so on) and could be viewed in GC and GCM. A few days ago, a user here in the forum talks the first time about not seeing older data anymore - so i checked mine and could see, that all not-from-a-garmin-unit-recorded extra-data was gone - no heartrate, no height-profile, no gps-track on map (only a straight line from start to end is shown).
I contacted the support via mail and described the problem as exactly as i can - today i've got mail from german support and the lady told me that 'imported data could be not compatible and because of that some data could maybe not shown in GC' - no single word about, that the data was already there and was shown perfectly. I replied and pointed again at the fact, that all missing data was already in GC and also was shown until last week.
Two findings at this case from today: Tried to re-import a older cycle-activity from Runtastic as TCX-file - this was not possible, GC always gave an error while importing - something seems to be broken here, as here in the forum another user also posted of problems when trying to import...
Second one - the date, from which old data on disappears, seems to slip forward! As stated before, at first all imported activities before 19th of November where affected. Right now, two or three days later, i checked again and the data from my activities from 19th of November and from 23rd of November are also gone. It looks that, if i'm right, all extra-data, which is not recorded by a Garmin unit, will be lost in a few days (got a Forerunner 645M at christmas).
I had to say that i'm very angry about this non-professional, standard-type-like answer from the support... :(
