In addition to my TR workouts (done indoors) I have two group rides per week. These rides are very consist in duration and intensity. I notice that TR consistently significantly underestimate the TSS for these rides on the weeks ahead. How is this affecting my plan?
Are you talking about upcoming group rides that you have added to your calendar? Arenāt those given TSS based on what you have put in for duration and intensity?
Iām pretty sure you can just put a custom value in for tss for the group ride option so you can set it to whatever you want
Welcome to the forum! 
Are you saying that the TSS for completed activities is off, or are you talking about planned rides?
Are you adding rides to your calendar manually, or are they a part of your plan?
I think I have the same or similar issue.
Iāve used the custom plan to create a week with the hard weekend ride converted to group ride and extended to 3h30 and the TSS is way too low.
Tuesday and Thursday add up to 162, leaving 108 for the hard group ride which should be estimated around 245.
And in a different view it shows as shorter:
I donāt think it will affect the workouts being selected unless you have a workout the next day that Fatigue Mgmt should be adjusting.
I would think that it affects FTP Prediction, in that it currently expects you to execute less work than you will.
Canāt you fix this by selecting a harder target intensity?
The only drop down is time.
And time keeps changing back to 1.5hrs
It looks like the AI is changing it after itās saved.
When you complete that group ride, and it syncs to TR, wonāt the TSS from that ride file fix this issue?
My guess is that they are seeing some version of the āMatched workoutā bug that you I believe were helping me with a couple months ago @Eddie (for repeating scheduled runs). Where it matches/displays different TSS in different locations when its a match. I have been un-matchingā¦ then TSS is consistent (based on my RPE input) for my run workout and is good everywhere and then deleting the āplanned workoutā for that day.
Yes @eddie what @ntisdell describes and @JoeX shows also happened to me for my A event and for any rides that are part of the plan but which I set as outdoor rides.
usually the outdoor rides will eventually correct to the actual TSS
However the A and C event rides didnāt correct at all and so I unmatched and deleted the events, keeping the done ride.
Ahh, okay. That makes sense.
@TimLawrence, is that similar to what youāve experienced as well?
But Iām sure when people schedule a 3.5hr ride in the calendar theyāll expect it to be what theyāve set, not under report planned TSS and switch to lower hours.
Iām not sure, as there is no matching going on.
I believe we have an existing bug report for this, actually. Iām double-checking now, but if I find one, Iāll add these cases to it.
If not, Iāll have someone from the team create one. 