Short answer: no, not from my side. Everything I know about your sleep and HRV comes in through Intervals.icu, so the Garmin to Intervals step is outside my control. Once it is in Intervals it reaches me straight away, so the hold-up was upstream of me rather than between us.
That is also why the 12:01 update needed nothing from you. The moment the complete data landed, it came through and your readiness and the day’s session were recalculated on it.
I added a C race to my calendar this saturday, but the training plan has not rebuild, and the training which was planned before adding the race is still in the calendar.
When can i expect the plan to “rebuild” around this? and should i have done something different when adding the race to my calendar.
I attend a lot of races and would like to add them into my trainingplan/calendar sometimes with short notice.
Also it does not seem like the TSS add up i the week with the race.
You did nothing wrong, and the race went in correctly.
Adding a C race is supposed to trigger a rebuild, and in your case it did. The rebuild fired six times this morning right after you added Tour De Aars. Every one of those runs read zero workouts from your calendar and so changed nothing, even though the sessions are plainly sitting there.
The TSS not adding up in that week comes from the same place. The plan is treating that week as if it has no sessions in it, so the number it shows you is not the number that is actually on your calendar, and the race load is not folded in either. I have been chasing this for a couple of days across a handful of accounts and yours is the clearest example I have, so thank you for the detail. I’ll get this fixed.
Thanks, that is kind of you to say, and the reports genuinely help.
On the indoor rides: I had a look, and everything Intervals.icu holds for you has come across. Over the last two weeks that is ten activities, all imported and all analysed, with nothing sitting in a queue. Your sessions arrive through Garmin Connect, and the one indoor ride I can find is a MyWhoosh session from 20 August, which came in as a virtual ride and was analysed like any other.
So the ones you are missing are not reaching Intervals.icu in the first place. IntervalCoach only reads what is already on your Intervals.icu account, it does not pull from training platforms itself, so a ride that never lands there stays invisible to me too.
Worth checking in Intervals.icu whether those indoor rides are there at all. MyWhoosh needs a route in, usually through Garmin Connect or Strava, or by uploading the .fit file yourself. If it turns out they are sitting in Intervals.icu and still have not shown up on my side, then it is mine to fix: give me a date and a session name and I will dig into that one.
As you can see from the snapshot i have indoor rides almost 4-5 days a week the whole winter.
But they also seem to come from trainerroad - trough strava. Maybe that is the problem.
Sabato non ho trovato il tempo per allenarmi, quindi ho chiesto al Coach di spostare l’allenamento a domenica, mi ha dato conferma di averlo fatto, ma di fatto questo non è successo (l’ho fatto poi io manualmente da calendario, nulla di preoccupante però magari a qualcuno può dare fastidio).
Inoltre una piccola nota (forse migliorativa): se ho letto bene ora il coach ti fornisce anche gli allenamenti per il core! Benissimo, ho provato a chiedergli di integrarli nei miei giorni di riposo (spoiler, non lo ha fatto) e ho provato a stuzzicarlo, chiedendogli di poter creare un modo per fargli sapere che in effetti ho eseguito gli allenamenti di core e/o stretching… bene, potrebbe essere utile integrare un “bottone” per fare sapere che l’allenamento è stato effettivamente eseguito?
Infine, ho notato che il feedback dell’allenamento, una volta eseguito, non sempre ti viene chiesto e potrebbe essere utile fornire un piccolo spazio per fare sapere al coach una sensazione personale, quindi scrivere un feedback, non solo fare tap sui due campi disponibili?
Sono una rottura di scatole, lo so! Mi piace restare a fondo nei meandri più nascosti
Strava’s API terms stop Intervals.icu from passing Strava-sourced activities on to third-party apps like mine. So a ride that reaches Intervals.icu through Strava sits there looking completely normal to you, and arrives on my side as an empty shell: no power, no heart rate, zero TSS. Those get skipped, which is why they are invisible to me.
The ten activities I could see over the last fortnight were the ones that came in by a non-Strava route, so “everything has come across” was only true of what I am able to see. Your MyWhoosh ride on 20 August went through fine, so indoor riding is not the issue in itself. The TrainerRoad ones are the category that arrives empty.
Worth an update rather than just a nod: that one is fixed and live now. The readiness swap now replaces the session the same morning’s run has already written, instead of landing beside it. So the shape you hit, a plan rebuild and a recovery ride six seconds apart both sitting on the day, should not come back.
Replying in English so the rest of the thread can follow, but grazie for three good ones.
On the move, you were right that the workout was not there, and wrong about the cause in a way that turned out to be worth a lot. The coach did move it. It ran the move at 19:04 on Saturday and confirmed the new date, and the move genuinely landed. One minute later the plan reconciler woke up, saw a change on your calendar, decided a ride did not fit Sunday, and removed it. It did the same again at 21:53. So the confirmation you got was honest, and a second process undid it behind the coach’s back. That is a real bug, because it makes the coach look like it invents things.
On core and stretching, two separate answers. The coach can put core or stretching on named dates, so asking for specific days works today. What it cannot do is hold a standing arrangement of “every rest day, from now on”, which is what you actually asked for, and it should have told you that plainly instead of asking you for dates twice and then telling you to ask again.
On workout feedback, the free-text box is already on my list from an earlier request, and I’ve added yours too, which moves it up. And you are not being a pain.
I give the coach a chance because I thought, may be this AI is smarter than all the others you can find here.
But why can the coach not remove a planned Bike workout for a Triathlon I am going to do instead. We talked twice in the chat that I am going to make short triathlon on Sunday and not the planned workout. He is confirming to make the change but in the calendar nothing happens.
For me this should be a basic function - replacing a workout with something new.
You are right, and thanks for the push, it found a real bug.
Two separate things went wrong. The coach told you it had prepared the deletion before it had actually run. That action waits on a confirmation step and it stalled there, so the wording you got was ahead of what happened.
Then adding the triathlon as a race could never have worked from chat. Intervals.icu does not accept “Triathlon” as a calendar event type, so we translate it to the bike before sending. The app does that correctly, the chat tool was handing the raw value straight over, and every attempt came back as a generic failure. Nothing you typed would have fixed it. I am fixing that now, and the same gap affects strength events.
Where you stand today: your Sunday is correct. The bike session came off on your later attempt, and the Willich Triathlon is on the 6th at 14:20 as a C event.
It would be nice, if you enter a Triathlon as an event, to enter the distances for each sports separate. Or is it impossible because of Intervals does not have a Triathlon as an event. Actual my race on Sunday is shown as a bike workout.
Thanks for your answer.
After finishing an ironman at age 60 two weeks ago, this will be fun.
You are right, Intervals.icu has no multisport event type and rejects a race event typed as a triathlon outright, so I map a triathlon onto the bike to make it save at all. That is why Sunday shows with a bike icon.
What decides whether you get a three sport build is the race NAME: anything carrying triathlon, Ironman, 70.3 and so on is classified as a multisport goal, and your weeks then come back with swim, bike and run plus brick work in the weeks before. So it is worth checking Sunday’s race is named that way. If it just says something generic, rename it and the plan will treat it properly. Making that a proper choice in the race editor instead of something inferred from the name is on my list.
Separate distances per leg are not there yet, and I would rather be straight about where that sits. A triathlon today is a dated multisport target: it shapes which sports you train and the bricks leading in, but it does not yet price the swim, the bike and the run separately for pacing or load. Per leg distances are the obvious first step toward that, and I have written it up.
Congratulations on the Ironman at 60, that is a serious thing to have done. Good luck Sunday.
Hi,
Sorry to bother you again…
Garmin calculates different VO2 max values for my running (44) and cycling (47). After a run today, Garmin pushes 44 to intervals and the coach interprets it as a decline from 47 and outputs a warning. I don’t know what consequence this might have in the future for planning sessions. I think that this is an inherent Garmin issue but it might affect the conclusions of the coach
Thanks for keeping up the great work
I’m dropping some new observations on Coach AI (CAI) after a Sunday race and a mid-week group workout.
Sunday Race & Post-Race Conflicts
Race Summary: The primary workout comments are getting better—no conflicting signaling in the main text this time.
Warmup Analysis: The comment on my 12-minute light warmup was pretty funny. It flagged the warmup as “very light,” seemingly trying to force a mechanical match between a quick pre-race routine and a planned 38-minute race. Classic “robotic AI” logic.
"Train Now" Logic Clash: The race comment explicitly recommended a 44-hour recovery window. However, opening “Train Now” immediately post-race resulted in a recommendation for a medium-heavy threshold session.
Mid-Week yesterdayGroup Workout (6x800m @ 5k Pace w/ 200m Jog)
Category Confusion: The feedback mixed up training domains entirely. It labeled the workout stimulus as “Anaerobic” (false for 5k pace VO2Max intervals), mashed together VO2Max and anaerobic terminology in the body text, and then compared the session to a threshold workout in the comparison section below.
RPE vs. TSS Disconnect: I rated the session difficulty a 4 (fo me easier than expected) , but CAI claimed the session was “harder than expected”—even though the actual TSS came out exactly equal to the planned TSS.
Weekly Load & Overall Takeaway
Macro Disconnect: CAI is still persistently prescribing training weeks capped at around 220 TSS, despite my baseline rolling average sitting at 420 TSS.
Coach AI seems fine as a general running fitness tracker, but handling regular weekly racing, adaptive load scaling, and accurate intensity categorization still seems like a heavy lift for it.
Not a bother at all, this is a good catch and it is our bug, not Garmin’s.
Intervals.icu has a single VO2max field per day, and Garmin fills it with the estimate from whatever you did last. So your series alternates between 47 on ride days and 44 on run days. My decline check compares today’s value against your 30-day peak and warns at a 5% drop, and 47 to 44 is 6.4%, so it fires on every run day even though nothing declined.
To your question about consequences: the warning on its own does not change a session, there is no rule that acts on it. But it does count as one warning towards the budget that decides whether other warning-level signals (a low HRV morning, a short night) are allowed to soften your day rather than just be noted. So on a run day it can tip the balance a bit earlier than it should.
The warm-up comment. You logged three runs on race day, and the analysis matched the 14-minute warm-up and the 9-minute shake-out to the race event, then judged each against the 38-minute race plan. The race itself was read correctly. On a day with several activities, race framing should attach to the one that plausibly is the race and treat the others as what they are. Filed to improve.
Train Now after the race. The race analysis wrote a 44-hour recovery window and Train Now never read it. It builds from the morning’s readiness and does not look at a hard effort from two hours earlier. That is a gap, not a judgement call, and I have filed this as well.
The 800s. The classifier only calls a session anaerobic when Z6 and Z7 time outweighs Z5, so your 5k-pace reps are landing above the VO2max band on the pace scale. Same thing you saw with the 7×4:20 last week. That is a boundary problem on the run zones and it is filed with both sessions as the test cases.
“Harder than expected” against your 4. The verdict was written from heart rate and intensity factor, and your rating did not override it. The part that matters more: from Monday to today your mornings read “recent workouts felt harder than expected, swapping to easier endurance”, so a wrong verdict softened your week. A stated RPE has to win over the inferred one.
The weekly load. Two things were true this week. A change I shipped last night had a bug that collapsed stored targets for athletes whose sessions were already on the calendar, and your plan rebuilt this morning inside that window: your next three weeks read 15, 30 and 30. That is fixed and I have rebuilt your targets: race week 163, recovery week 265, then Build at 441, 460 and 485. The pattern underneath, race week then recovery week then race week again when you race every one or two weeks, is what I wrote up after your post on the 24th and is still open. For the record, your six-week rolling load is 379; 420 is CTL times seven.
It seems to be a bug in ICU, maybe in Garmin too. It seems to me that stopped pauses are interpreted incorrectly. So I’m doing a 60m stride (let’s say 5-10 seconds), after that I’m pausing the workout on my watch, then walking back. It seems that the walk time is interpreted as a run with a final pace.
For yesterday, it should have been only 30 seconds in the Z7 pace bucket (Strava shows it correctly).
Good catch, and it explains yesterday’s label. For runs the stimulus classifier reads the pace-zone time buckets Intervals.icu computes for the activity, so when the walk back after a stride is counted at the stride’s pace, those five minutes of Z7 land straight in our anaerobic decision. I’ve linked your bug topic on our ticket. Once the buckets are corrected I’ll re-run the analysis on that session so the label follows. The zone-boundary issue from the 7x4:20 last week is separate and still on our side.
