Update on this- we’ve fully implemented the fix for rides receiving unusually low TSS values, which related to how some devices saved HR data. The system is currently reprocessing all rides with previously estimated TSS to fix any existing errors. This might take a bit, but if you had rides with TSS values that seemed low, they should straighten themselves out sometime today. Any new rides with estimated TSS should also receive correct estimates.
If you still see anything that still looks anomalous after later today, or if you’re still having the issues saving preferences some athletes reported earlier, please send an email over to email@example.com so we can log the specific issue and make sure it’s included in the fix.