My SeasonMatch seems to be stuck on week 52 for the past couple of weeks, which isn’t particularly useful early in the season lol. As best I can remember it started acting up 2-3 weeks ago, and worked fine prior to that. I definitely used it with expected results earlier this season.
Is anyone else seeing issues? Could someone from Trainerroad take a look?
Hey guys, if you set your comparison season to all of 2025 (which is first on the drop down list), we will use all 52 weeks of 2025 for that comparison.
SeasonMatch compares PRs at the same point across different Seasons, based on how many weeks are in each Season you’ve created. In this case, if you’ve selected Calendar Year 2025 as your comparison season, it will include all 52 weeks, even the ones that haven’t happened yet.
Since you’re still in the early part of 2025, SeasonMatch is currently comparing your full past Seasons to the entire 2025 calendar year, which includes future weeks.
We realise this is confusing so we’ve passed this onto the team to fix. In the meantime, here’s what you can do:
To compare your training up to this point in the year, create a Custom Season that starts on Jan 1, 2025 and ends on today’s date.
Let me know if that works. If you have questions for me, please don’t hesitate to shoot them this way!
I also agree that the bit about 2025 is confusing, so thanks for trying to improve that! It seems to make sense that if comparing dates which haven’t occurred yet, only the to-date should be used.
I’d used the same work around the other day to get around the issue. But I don’t believe this behavior is how season match previously worked.
I’ve always created a new season at the start of each calendar year for the full year, and then used season match during the year when looking to compare this year to previous years for the same point in time. If you unclicked the season match, then you’d get the full year for the previous years compared to this year to date. Now the season match is stuck at week 52, and you have to use the work around or you get the full previous years power curve rather than how season match previously worked in limiting those previous years to the same point in the year as it is currently.
Seems something has changed on the backend somewhere that has broke the season match as to how it previously worked?