I’m experiencing an issue regarding the Load (TSS) values when syncing workouts from TrainingPeaks to Intervals.icu.
Even when sending the correct TSS value (e.g., 110) via API, Intervals.icu seems to either ignore the uploaded value or recalculate it internally, resulting in a different number (e.g., 109).
I have checked my settings, but even when I explicitly send the load data, the platform appears to override it.
A few questions regarding this behavior:
Is there a specific field or flag in the API that I should use to ensure Intervals.icu respects the “source” Load/TSS instead of recalculating it?
Does Intervals always prioritize its own internal FTP/Zones settings over the data provided during the upload?
Is there a way to lock the Load value for a workout via API to prevent auto-recalculation?
This discrepancy makes it difficult to keep both platforms in sync for athletes who use TrainingPeaks as their primary planning tool.
Has anyone found a workaround or a specific mapping to fix this?
Ok. Apart from the fact that the deviation is minimal, the calculation is correct in intervals:
Load=(NP/FTP)^2 * time
For the first workout
(170/207)^2 x 83 x 60/36=93,301
No, there’s no mistake. These small differences are the result of
rounding errors; round or round down/up
zone definitions; is a zone including the starting or the end value?
small difference in TSS calculation caused by TP not publicly releasing the exact TSS formula. You will see larger differences in NP for intervals, caused by a different way of calculation. NP for the entire activity should be correct with the same level of accuracy
What is considered moving time/stopped time?
These small errors will not make any difference in the longer run and can safely be ignored.
Perfect, thank you so much for your help in understanding the issue. I’m honestly not sure why there’s a TSS of 110 on TP (set by my coach), but as we discussed, it’s not that important.
In another post, I’m discussing the sync duration issue: on TP it shows 1h 59m 10s, but on Intervals, it’s only 1h 59m. This difference causes the workouts to keep re-syncing/duplicating, but I’m addressing that in the other thread.
On the other thread, the duration shows 1:59 (Intervals) on the workout header without seconds due to display size, but it you look at time in zone it adds up to 1:59:10 (51m15s + 55m + 10m + 2m55s = 118m and 70s = 119m10s). However, you show planned workouts and not the completed activity, so not sure where the duplication you refer to comes from.
