Hey Guys, I also have the issue every now and then…
also already tried fixing the fit file but without success.
Today it failed again, and this workout actually contained 30second intervals, so that could be a direction to start looking (saw this mentioned above somewhere).
But it really sucks, the only solution was to manually create a new workout in garmin and simply enter time/distance/calories etc without any further detail.
I think (being in the software dev area myself) that this could easily be pinpointed by the Zwift team based on a few files we can deliver + a test API garmin surely has available to test with files, which then returns success or errormessages on where it goes wrong…
Glad to help so we can get this issue sorted out, because i’m clearly not the only one
so yesterday I did a normal ride (no structural workout) and it synced flawlessly to Garmin Connect.
I’m sure that this didn’t contain any specific segment like a 30 second sprint or something, so for now, this could be a direction to pinpoint the issue.
I’ll keep an eye on it, especially during structural workouts to see if they fail (and if <1min segments are in it). This week I rode 2 workouts containing 30 second short and heavy segments and both failed to upload to garmin… I guess we’re getting closer…
This has happen with me too. I logged a call @Zwift just told me to reconnect to Garmin and to test my download speeds!!
I told this is not the issue it definitely a Zwift problem in the production of the FIT fie, as when I download a new fit file from zwift.com and try to manually upload it, it errors again.
Come #zwift sort it out at £12.99 this is not a budget service!!! Interoperability using the standard FIT format as advertised should be a given and is spoiling the user experience .
#Zwift this does not happen with “TrainerRoad” I am seriously thinking about taking my customer elsewhere #fixtheerror please
workouts (also with <30seconds segments) sync perfectly to Strava, but not to garmin connect.
this could easily be tested with fit files + the garmin connect developer API environment.
However, it could be something in Garmin’s API where <30 sec segments are not supported and that they would need to adjust the API contract on their side…
So it’s not simply a Zwift only problem I think…
I just checked garmin connect workouts and there I can create segments of <1min without any problem…
Next, I installed Golden cheetah, and imported one of the failing files.
This is the 8minutes rolling TT from the Etape du tour - part 3.
Errormessages are : Invalid end time (on lap 0,1,15,25 and 35)
15, 25 and 35 are 30 sec highpower sprints… lap 0 and 1 are 5 minutes warmup laps… so the <1min theory doesn’t seem to be correct all the time (but it does for 15,25,35)
Also, there are other laps <1min that don’t error on import.
imported the file in GoldenCheetah but I can’t see anything special on these bad laps compared to other laps (but maybe since these ‘bad’ laps are ignored, they have been removed and I simply don’t get to see them in the json file.
Anyone knows of another way to open a .fit file without some import magic is happening, so you can see the raw data that’s in there?
Same problem here. Did a Zwift ride yesterday, which included some short sprints and a 1min all out effort. The ride ported to Strava just fine but it didn’t port to Garmin connect. Downloaded the fit file from Zwift and Strava but Garmin connect reported an error when trying to upload it.
I managed to get it uploaded to Garmin connect after using the fit file tools corrupt time fixer. However, the power curve data was missing, and it didn’t recognise what was a new 1min PB
