Apologies, there’s probably other similar threads.
As an experiment I added an “AI workout” 3 days from now, on a day where there’s currently nothing scheduled. I went with Endurance, dynamic duration, letting it choose. It came up with Vincent, 1hr15, “Easy”.
The result? My AI FTP prediction (26 days from now) went from 313W to 317W!
We’re looking into a few cases where FTP predictions have been jumpy. I’ll add this one to the list.
Thanks for the heads-up!
Feel free to add my calendar to the list as well. Reducing my first VO2Max workout of the coming block from a 6.0 to a 4.8 makes the, already too optimistic, prediction of +4.2% jump to +10.9%.
So you manually changed it from a 6.0 to 4.8, right?
Was it the same type of workout (long suprathreshold)?
Yes, I bumped it down manually to something I might be able to do on a good day. Same type, from Haw to Monterey.
Another bug… one assumes.
Tonight I was scheduled King. I did King. It guessed it would be easy. I marked it as easy, because it was easy.
My predicted FTP 26 days from now jumped up from 313W pre-workout, to 324W post-workout.