Skip to main content

Re Open to : Improve post-race status transition and "Race B" activity logic

Feature Request

https://intervalcoach.featurebase.app/p/improve-post-race-status-transition-and-race-b-activity-logic

Hi Martijn,

Just wanted to let you know — unfortunately the fix doesn't seem to be working, the system is still behaving the same way.

After yesterday's race, the "race" activity is still being treated as a workout leading up to the race, and the following recovery is read as a random performance drop / health disaster :)

If you get a chance to look at yesterday's data — it's a gravel race again, and everything is correctly linked/paired in Intervals.icu. Not sure if this is something on my end or a system issue.

Thanks,
RJ

Posted by Radim J ·
Status: Completed2 comments

Log in to comment and vote

Comments2

  • Martijn Russchen

    Team•

    Aug 15

    Quick follow-up: the fix is live. I've re-run the analysis of your EPIC RIDE — it now reads as what it was, a completed race, with a recap comparing it to your similar long ride 8 weeks ago. The walks on the days after now read as planned post-race recovery too.

    From your next race onward this happens automatically when the activity syncs, through the same code path I just verified with your data. Thanks again for pushing on this.

    Cheers,
    Martijn

  • Martijn Russchen

    Team•

    Aug 15

    Hi Radim, thanks for reopening this. You were right, and I owe you a straight explanation.

    I checked your Aug 12 ride: everything on your side was perfect. The A race was on the calendar, typed gravel, and the activity was paired. The July fix itself was correct, but it turned out to be wired into only one of the code paths that analyze activities, the one I used to verify it, while the path that runs automatically when your ride syncs never got it. So it looked fixed on my side and wasn't on yours.

    I'm moving the race detection into the shared path both routes use, which also fixes the days after a race being read as unexpected fatigue instead of planned recovery. Once it's live I'll re-run the analysis of your EPIC RIDE so the stored recap is correct, and I'll confirm here.

    Thanks for the patience and for the precise report, twice.

    Cheers,
    Martijn