So here is a weird one: My last couple outdoor rides using my Karoo2 have synced to TR fine, however, TR is subtracting the “pause” time from the data and thinking I rode for a shorter time than I did. Let me offer an example:
Today I had a 2:15 endurance ride planned by Dynamic Endurance. Cool. I went out and rode for 2:18. That was MOVING time. I had about 12 mins of “paused” time (when I view the details on the Karoo dashboard it shows “paused” time as one of the metrics), so the total activity time was ~2:30, but when I go to rate my RPE for the ride I get a message asking why I stopped my ride early, and then see that in the ride summary TR thinks I rode for 2:06, when in fact it was 2:18. The weirder thing is on the calendar it shows 2:18 but ride details go to 2:06. See the screenshots below:
I checked my last few outdoor rides and it did the same thing; subtracted the non-moving time from the moving time, not the total elapsed time.
Anyone else experiencing this with the Karoo or other head units?
EDIT: I will add that Strava is parsing the .fit file fine. It shows the correct moving time/average speed, minus the usual ~0.2-0.3kph Strava tax 
1 Like
Yes I noticed this with my Karoo 3, with an outdoor ride unassociated with a workout. I ignored it since I’m not following a plan anyway. There’s been a bit of talk on here about TR “punishing” pauses indoors so maybe it does the same thing outdoors now?
Hey @PilotGuy74 
I’l look into this and get back to you.
Thanks!
It’s a weird one because if it’s subtracting any non moving time from the moving time rather than the elapsed time, a one hour workout/ride with a one hour coffee stop at the end before a short hop home would basically be null and void.
Hi! I’m running into the same issue. I do a lot of workouts outdoors, and after an interval I usually stop briefly to take a gel or put on a vest. That drops the average interval power by about 10–20%, which I’m pretty sure has a big impact on the AI model.
How are you planning to handle this? Will past rides be corrected automatically, or will I need to reimport them?
It feels like a pretty critical bug, since it can easily undermine the whole point of relying on the AI.
Which head unit are you using to record your outdoor rides? Is it also a Hammerhead Karoo 2/3
Karoo 2.
Overall I think the data is there, but TrainerRoad messes something up with the laps/intervals.
On Hammerhead and Strava the laps are following what I was doing during the ride.
The highlighted Lap 7 is shifted in time roughly 2m30s
1 Like
Yes, I went back over some of my past outdoor rides and it only seems to affect outdoor rides associated with a workout. “Free” rides seem to be ok. For example I did a chill outdoor ride with the Mrs a couple weeks back and stopped for coffee for probably as long as we rode and it counted all the moving time. If this was associated with a workout I think it would have all canceled out…
Hey @PilotGuy74 I was able to check on this and all is well.
If you paused during their workout, this will not be the same.
TR displays moving time, and if you hover over it, it will give the total time.
Hi @Caro.Gomez-Villafane Thanks for looking at this. I don’t think the issue is resolved. The moving time for this particular ride was ~2:18 (Strava treats pauses differently so it is slightly off). The total (elapsed) time was ~2:30. I don’t know if you guys can have a closer look at the .fit file data, but TR is subtracting non-moving time from MOVING time, rather than total ELAPSED time from outdoor rides associated with workouts. Every other place this ride uploaded (Hammerhead Dashboard, Strava, Intervals.icu etc.) shows the moving time as ~2:18 and elapsed time as 2:30, as well as the correct metrics (TSS, NP, Avg speed, etc.). I did not manually pause this ride at any point. All pauses were due to stoplights and other normal outdoor ride stuff, etc. Strava data below:
I’ve looked at several of my outdoor rides lately and all the recent ones I looked at associated with a workout exhibit this behavior. I did an outdoor ride again yesterday (white -5) and actually loaded and followed the workout on my head unit (for endurance I usually don’t load/follow the workout) to see if it made a difference and… it did not make a difference. Total activity time was ~1:13, moving ~1:08 (stoplights etc) and TR said the duration was ~1:03 for the purpose of calculating the metrics (TSS, NP, Avg speed, etc). It’s clearly treating moving time as elapsed time and subtracting any non moving time.
I opened a support ticket regarding this last week. If you want to continue there I’m happy to provide more info, rather than prolong the thread, however I think others may be having this issue as well, as evidenced by replies above. Thank you again for looking at this, but can you have another look please?
Cheers,
gm
@Caro.Gomez-Villafane I will be honest with you - it’s very critical bug as the .fit file is parsed wrong leading to workouts being consider “Not finished” or “Too Hard”. This literally discredits the whole point of relying on AI in terms of the intensity and FTP detection as TR thinks that the workout was too hard for me.
I don’t see any reason why in TR system I see the intervals start/end at different time than hammerhead/strava (messing the avg power etc.)
Can we ask you to escalate it to the tech team so they can give it a look?
1 Like
Let me take a deeper look
1 Like
Are your outdoor workouts getting labeled as such?
Note: For the workouts being interpreted as ending early as per the first screenshot from @PilotGuy74, this is actually a known bug that our team is actively working on fixing.
1 Like
they are. Maybe it’s a separate problem.
Keep in mind that a root problem is that because of this whole moving time subtraction etc. the actual laps are rubbish.
- This is the actual lap I recorded on Karoo 2
- Here is the same lap but in TrainerRoad
That’s my main problem. According to TR this lap was done with 280W, but in reality it was 297W which is a huge difference. Because of the bug with TR parsing the .fit wrong all the laps are misplaced and the whole workout (from the intervals point of view) doesn’t make sense.
1 Like
I did a little experiment last night. I set “Scotty” as an outdoor workout. It is a 15min “commute” ride. I loaded it up and rode ~6m down to my cycling club’s preseason meeting. My ride paused for about 90 minutes during the meeting. I rode back home for ~6min and uploaded the ride. My hypothesis was that TR would cancel the entire ride out because the paused time exceeded the moving time. What actually happened is that on the calendar summary, TR showed the correct total moving time of 12:31, HOWEVER, when I clicked through to the summary, it only counted the moving time before the first big pause, showing the moving time as just over 6 minutes. There were two short (~1min) pauses at stoplights (the first one being about 40 seconds in, the second about a minute and a half in) on the way to the meeting, so I’m not sure what exactly is going on here…
Just to experiment further, after looking at the uploaded data and seeing the above behaviour, I deleted the ride and the planned workout “Scotty” from TR, and re-synced the ride from the head unit, disassociated with a workout. Lo and behold: with no associated workout, the total time was correct on both the calendar and deeper ride summary pages at 12:31 total moving time.
@Caro.Gomez-Villafane Thank you and the team for looking into this, and acknowledging that it’s a known bug.
hey @Caro.Gomez-Villafane ! Do you have any updates from the technical team?
It’s like you read my mind! haha Yes!
Update: team has created an issue for it and will have devs on it. I don’t have an ETA for it though as we’re tackling things on high to low priority basis.
