Show moving time on cycling workouts
This has been an issue forever. Trainingpeaks only shows total "Elapsed Time". There is no option to even display actual "Moving Time" vs. "Elapsed Time". When a ride is synced to a workout, the Planned vs. Actual time is not quite accurate as it counts elapsed time towards the planned time, not moving time. There are many reasons why one would need to stop mid-ride - to fix a mechanical, relieve oneself, eat, change layers, or just wait up for riding buddies. This is true especially in long rides.
This non-moving time is included in the total riding hours for the week, as well as counting towards compliance for a workout when compliance is calculated by time. I don't find that to be very useful or helpful.
At least provide actual moving time as a display field, and ideally allow the option to calculate total hours and workout compliance by actual moving time.
-
MELISSA OCAMPO commented
I can confirm this is still an issue in July 2026 with a Garmin Edge 1050.
I worked with TrainingPeaks Support and analyzed the original FIT file.
The FIT correctly contains Auto Pause events, Total Elapsed Time and Total Timer Time. The structured workout executes correctly on the Garmin device, but the Structured Workout Overlay becomes offset by exactly the accumulated Auto Pause duration.
This appears to be a limitation of the current overlay alignment rather than a problem with the FIT file itself.
An optional "Align Overlay using Timer Time" (or Moving Time) setting would solve this problem for outdoor cyclists performing structured workouts.
During my support case, I was advised to manually shift the overlay using the left/right arrows or edit the activity after every ride. Unfortunately, neither approach is a practical long-term solution. The overlay adjustment is temporary, and manually editing every workout is unrealistic for athletes who regularly perform outdoor structured training.
Outdoor cyclists routinely use Auto Pause for safety, traffic, nutrition, hydration, mechanical issues, or brief phone calls. These are normal parts of outdoor riding and should not reduce the usefulness of post-workout analysis.
Since the FIT file already contains both Elapsed Time and Timer Time, allowing users to choose which timeline is used for overlay alignment would preserve the current behavior while providing a much more accurate analysis for structured outdoor workouts.
Thank you for considering this suggestion. I hope it can be implemented in a future update.
-
Pg
commented
The same files from Strava and Garmin will show the time where speed is not = 0 and so I suspect this could be done in Training peaks
New Beta charts has a 'moving duration ' but it does not pull this 'moving duration where speed not = 0 km/hr "
TP Beta chart with moving duration same as duration (1:23) https://app.screencast.com/FhoOJMBD0yMHg
strava for same workout with 55min = https://app.screencast.com/77MKkVM3JrMHP