I have almost the same thing but from strava. Everything was syncing very well. Yesterday evening i started a training plan, did the ramp test. This synced fine. I then jumped on the bike for an outdoor club ride, but it never synced with strava. So today I tried to manually upload the fit file from my element. It said it was uploaded, but still no where to be seen! I’m wondering if it’s something to do with being in the training plan or the change strava made as adds appear as of yesterday!
Yeh, from looking at other comments it looks like if you do a ramp test and then do an activity straight after it’s causing issues, i’ve contacted support, hopefully they can sort it out!
Hmm interesting, that’s strange.
I think tonight I’m going to do Zwift without running the TR app. and see if that syncs over.
I was going to clarify my use. In general, I “keep” the file as created by the app that controlled the trainer,
If I am doing a Zwift ride, fondo, etc., then I only run Zwift (no TR).
- That ride syncs to Strava, and then TR pulls it from there.
If I am doing a TrainerRoad workout, I launch TR and pair all devices.
Then I launch Z and pair all devices (making sure that “Controllable Trainer” is not selected, so TR is the only one adjusting the trainer).
I do the workout and let the TR workout finish and close TR. The TR ride uploads to Strava, and I delete if from there right away.
I only want Zwift “rides” in Strava, not the actual TR workout file version of it (vanity for mileage and climbing ).
Once the TR file is deleted from Strava, I finish and close Zwift, making sure to add “TR - Pettit” or whatever for the workout name into the Zwift event title at closing. The Zwift ride uploads to Strava (I keep that one there).
The TR ride also uploads to the TR Career and Calendar pages (I keep that one there, since it was the controller for the ride).
The only “extra” work is making sure to close in the proper order and deleting one file from Strava. Easy habit once you do it a while
Those seem to work fine for me.
The issue we had is doing a TR workout and then doing a Zwift ride after.
So I did exactly as you said in “#2” and it worked exactly as you mention.
However, then I do exactly as you say in “#1”, but it does not pull to TR.
The days where I do just “#1”, TR seems to pull the Zwift workout from Strava just fine.
(Pure speculation mode engaged:) I think it has to do with the way they try to prevent duplicates in TR. I have had a few rare cases where I needed to trigger TR to pick up a Strava ride, but it isn’t often.
I wonder if it has to do with the date and start time of the files involved, and TR likely seeing them as “identical”. It seems they are playing the angle of preventing duplication more than allowing possible doubles. As such, there could be cases of truly separate workouts, but TR seeing them as “the same”.
I think you’re correct.
I just did a Zwift Ride (with no TR ride before hand) and it synced over to the TR calendar perfectly.
Looks like i’ll have to decide whether to do a TR workout or a Zwift ride from now on, and not both in the same day. It’s a shame because i like doing a Zwift ride after an FTP test etc. I want to track my TSS accurately, i’m becoming obsessed with TSS, probably the wrong thing to do, but it’s really working for me at the moment so I’m gonna keep doing it, the new calender would be perfect if it synced all rides!
It’s not impossible. You can still get what you want right now, it just will take a few more steps.
I have the same issue. Using a macbook pro. Unable to sync my ride from Zwift with TR. Have tried editing the title in Strava, manually importing the gpx file from Strava, manually importing the fit file from Zwift, all without success.
For me, this is a “it just has to work” feature with regards to syncing rides from various sources if I intend to use TR as my single source of training analysis. Any help is appreciated, cheers.
I have been in communication with support about this, it seems if you use TR then Zwift afterwards it might not upload because the time stamp is too close together. All my other Zwift rides have uploaded, but these a done on different days to TR. I hope TR manage to do a patch for this in the future.
That seems to be the case here. Rode on Zwift today, ride synced without issue. The previous ride was immediately after a TR ride.
This bug still has not been fixed. It isn’t Zwift-specific; any ride from Strava after a ramp test will not sync correctly. Any attempt to upload the ride manually leads to an error message that it is a duplicate. This means the ride has synched but it does not show up in the calendar or as a past ride. Surely the fix is not so hard that this bug is still present two years on? I do not want to have to contact support every time I do a ramp test and then ride after in order to get the ride to show.
Hey! We have this fixed in the beta version of the new TrainerRoad app if you want to become a beta tester and not wait until RN goes to production!
I don’t think the problem has anything to do with the mobile application. This is an issue with syncing - the mobile app is not involved.
The fix will be released when both mobile and desktop apps are updated soon, but getting on the Beta version will just give you access to that fix sooner! Otherwise, you should feel free to sit tight for the update on all platforms shortly.
This sync issues occurs with the website, so I fail to see how getting the Beta version of the mobile or desktop apps will fix it.
Sorry for the confusion, happy to expand upon that!
So we have duplicate logic within TrainerRoad to filter duplicate rides from syncing into TR (e.g. if you record your ride on your Garmin/Wahoo at the same time as your TrainerRoad ride, you have Ride Sync set up between TR and Garmin, we’ll block the Garmin/Wahoo ride).
How the duplicate logic works is we take the start time and duration of ride A and block any ride that starts within that window. Because the Ramp Test’s start time is showing up as when the cool down begins, there’s an extra 15-20 minutes of time after the Ramp Test where we’ll block rides.
This ‘duplicate language’ bug has since been fixed on desktop versions, and has now been fixed on iOS Beta, although we see you use an Android device for Ramp Tests and workouts. We can get still around it if you hit up support and send us the file for the ride that was blocked, and we know this is arduous to have to do all the time, but we will have Android beta ready soon that prevents you from having to do this!
The bug you describe sounds like it would be very easy to fix. Why has it taken two years (longer for Android)?
Sorry for the delay, definitely wish this stuff was quicker and less complex to work out than it is! We’ve implemented numerous features and fixes since the last mobile app that were higher priority, but we’re glad that the mobile updates are almost ready!