Rizzi
February 16, 2026, 2:35pm
9
Pbase:
adding a run as an extra activity doesn’t seem to trigger the fatigue management the way I would expect. I go in and rate the runs harder than they felt in order to get the TSS in line with what I see in TP and intervals, but even then, it doesn’t seem to trigger a yellow/red day like I would expect.
Vlaho_Sabljic:
Just did HM at maximum effort, my previous longest run was shorter and lower effort.
TrainerRoad think I should be doing harder climbing workout today. I am thinking either full rest or 30min recovery spin.
Not very confidence inspiring.
According to Nate Fatigue management is not driven by AI but by a functions of TSS…and for runs I think the TSS component is just derived from duration (but not intensity or run power or GAP or HR) which these examples show. @Nate_Pearson would like to hear which factors drive run fatigue (so we know the dials we have and the dials that don’t work) and what changes are planned.
@caro in my above quotes you see other data points to this discussion https://www.trainerroad.com/forum/t/trainerroad-ai-beta-testing/107104/4160?u=rizzi and your involvement here:
Hey @Rizzi , sorry for the late reply here!
I was able to confirm that this is not a bug but rather how runs have worked since the start of our Fatigue Detection system. However, this is now causing an “issue” with the ability to see what impact they have on the future. All of this to say, this is not how we want it to work permanently, but I don’t have an ETA of when we’ll change it
1 Like