Workout pauses all of the sudden mess up laps

Long-time TR user here. Yesterday I ran into something that I haven’t seen before, and I would be curious to hear if it is a bug or a new “feature” – if the latter, then it’s a really unwanted one!

On Tuesday I did a 6x10min SST ride with short pauses on my TT bike. I did a couple of micro breaks (one at 5min to fetch my water bottle I had forgotten, one after the second 10min interval to reload the movie I was watching that was stuck on buffer). On the TR app it looked like this:

However, as usual, this did not reflect on the Strava file – on it, no breaks are to be seen. This is how it has always been:

Then, yesterday, I did the same workout but this time 6x11min to get some TTE progression. This time around I had a lot more pauses, especially in the warm up, due to my tinkering with my TT bike fit. I completed the workout and the TR file looks like this:

The strange thing is that yesterday, Strava all of the sudden includes the pauses into the file:


This would not otherwise be a big issue, but it really messes up Strava laps as a consequence. I guess Strava takes the laps directly from the TR workout but doesn’t take into account the pauses. So for eample if you have 20min warmup at 250W followed by 1min at 400W and 10min at 150W, but then you take a total of 4min of breaks during the 20min warmup, Strava now thinks that the first lap was the first 20min of total time (so only 16min of riding), the next lap was the next 1min (which in my case was not 400W because I was still doing the 250W warmup) and so on. See the Strava laps here:

This is super annoying because the Strava files are then imported into intervals.icu which I use for analysis, and consequently the laps will be totally wrong there.

Is this a bug or an intended new feature? If intended, could it please be fixed back into how it used to be? I don’t see anything good in this update to be honest.
Oh, and these two workouts are manually created in workout creator as are all of the workouts I do. Could this be a cause of the problems?

Have you already considered and evaluated the possibility of data transmission/connectivity issues?

The cause could be too many devices or other kinds of interference messing up the connection or low a low battery if you e.g. use a power meter with a coin cell.

Well I don’t see how that could be the case? The problem is clearly in the TR/Strava interface. My workouts on TR look the exact same as before (see the included TR screenshots) but how they display on Strava is different (before the pauses that TR recognizes were not included in the Strava file, all of the sudden they are there). I always record using the same phone and used the same Wahoo trainer for these two workouts.

Update to latest version. See my comment Feeling EXTREMELY frustrated with AI FTP detection/plan! - #282 by bradskuse

And my post above that where I described the same issue.

Sorry, looks like I wasn’t quite awake earlier and misread your text. I was under the impression TR would also show breaks which you didn’t do - which could have been explained by these drops of data. If you did all those breaks and they show up differently on the services, that’s clearly something else

Thank you very much, that is precisely what I meant! Can @eddie chime in here and explain the situation? Can the “feature” be debugged away?

I realise that I am probably in the vast minority here that I subscribe to TR only because it is a very convenient way to control workouts on my trainer – I have no use for AI features or anything, I just build my own custom workouts using Workout Creator and then use the phone app while riding. I have always thought TR worked wonderfully well for this, but the botched up laps are extremely annoying and could push me to using another trainer controlling app (I am sure there are a few decent ones available).

Which version of the app are you on?

2026.29.1

I’m bringing this to the team now. Hang in there!

This issue should be fixed! Take a look and let me know if anyone has any lingering issues..

1 Like

Thank you very much! I will test it today or tomorrow, will confirm if everything works properly :slight_smile:

Nope, same problem still… Should there have been an app update for this? I didn’t see one on App Store.

I think there may have been two issues related to workout pauses that I thought was one issue. :anxious_face_with_sweat:

The good news is that the second issue is being worked on now and should be fixed very soon. I believe that we might also reprocess past activities that were affected by this issue, so that will hopefully make things right.

I’ll follow up here when I hear more about this next fix. :technologist:

Hi @eddie and @visa.k, I’m having the exact same issue. It’s very frustrating. I’ve lodged a support ticket so don’t want to be too annoying but yeh, it isn’t useful to have the whole file, lap data, Strava feed with image etc ruined because you need to fill a bottle, answer the front door or you decide to backpedal for 5 or 10 seconds to get a bit of recovery between VO2 intervals if you’re on an off day.

It was totally fine the way it was imho. If the team at TR want to have this feature as a display option only then that’s fine but as it is its ruining feeds, lap data, average power conflating elapsed time with moving time on the Strava feeds, and other quirks too…

Hoping for a resolution soon. Many thanks for posting this in the forum…

Dave

Thanks for chiming in! My exact thoughts.

TR team have done something to fix this but this still isn’t right, the bug is just different. I took a deliberate ~1min pause today at around 30min. On the TR app you don’t see a thing:

However, when I look at Strava (and Intervals) this looks totally different. It displays the pause, and then it mystically truncates the ride so that the 1min pause is included in the 1:30 I rode, so there’s a whole 1min of riding totally missing from the file! Notice how the laps are again totally wrong.


So yeah, why not just go back to how this was before? Why include these pauses in the power file at all when all it causes is these stupid problems?

100!

It’s totally ruining the integrity of the FIT file that feeds to other platforms, so much so the data is almost unusable on TP or Strava because it overlays the fields (ie power, avg power, lap/interval time, elapsed time and time under tension or ‘moving time’ incorrectly.

If I’ve gotta start using my Garmin to get a proper file for Strava and/or TP it’s all getting too hard. Hopefully @eddie will be able to have his team sort the problem.

I like TR a lot and think some of the improvements in the last couple of years have been great, but this would be enough to spoil the user experience for me if it wasn’t fixed.

Thanks for continuing to report on this. :handshake:

I’ve reported the issue about .FIT files to the team, and hopefully they can take a look today.

Was this always a part of the issue, or is this something that popped up after the fix in TR?

Thank you! By “Was this always a part of the issue”, do you mean the messing up of laps and fit files? Because that’s been the same ever since my OP post.

Yeah, that’s all I was looking for.

Thanks!

I believe we have a fix in place for this now.

@visa.k, it looks like the issue with your workout has been resolved.