I had this issue, and they told me to use the next Tuesday’s workout. Actually this time when I did AI FTP, but before AT had done it’s thing I briefly had the same workout this week and next week!
1 Like
Hey @HLaB! I was able to prompt the replacement of your Ramp test with the appropriate Workout by heading to your Calendar, and clicking the annotation that marks the start of this new Block.
Once I clicked “Build”, the box below popped up. I hit “update” which refreshed the Plan, and ultimately replaced the Ramp test as expected. This is an issue that the team are working on, but this is an effective workaround in the meantime. Let me know if anyone has any questions about this! 
2 Likes
Quick question: Will AI FTP Detection work well with the beta Polarized plans?
Does for me!
1 Like
For the record, AIFTPD looks at ALL cycling workouts imported into your TR Career. This includes all TR workouts & plans, but also all “outside” workouts, rides & races.
3 Likes
Just a quick question on FTP detection thresholds.
Just over 2 weeks ago I started a plan so did the detection and got 219w. Plan was cancelled as work and builders meant I struggled to get going for a week.
Started ssb1 today and after 45 minutes of Goddard I got a message to auto detect FTP as it had changed, gone up a massive 1w (<0.5%) with only a couple rides since last detection.
My question would be what’s the threshold to trigger the update? Only thing I can think of is that it flagged as it was a new plan but it was a pretty current auto FTP before today.
I would have thought AI FTP Detection would do some combination of all but #3.
Hey @firemunki
By consulting with the team, it’s possible that you discovered a bug that triggered the use of AI FTP Detection twice within the 28-date gate.
As far as the 1-watt increase, although not a massive change, AI FTP Detection did detect a change in your FTP since your last FTP change. You’ve actually had a pretty good amount of outdoor riding, which led to the increase.
So if anything, kudos for the increase while having to deal with work and builders!
3 Likes
Im finding the 28 day detection a small problem where each time I update I am slightly later than last time so while I might like to update on Mon at the end of a rest week it drifts to tue, wed,…mon next week and I cannot pull it back. A 27 day limit would alow a bit more flexibility.
9 Likes
Great point. I’ve noticed the same.
2 Likes
AI FTP Detection should actually be working like this..
The day you use it is technically “day 1,” and the time gate opens in 27 days + however many hours to midnight. This means that you should be able to run a new detection sometime on the 27th day. It just might be later in the day, depending on when you ran it last.
What about an option to run it at the end of every rest week, or the start of every block?
That could be a good idea, but blocks aren’t always four weeks long, which could cause issues. 
Yeah, I was thinking you could have an option to allow for a check at the beginning or end of each block instead of every 28 days.
2 Likes
Are you expecting that to be longer than 28 days? Some blocks are shorter..
It seems odd to run AIFTP after a rest/recovery week. Blocks are typically 3 weeks of “work”, so it would appear that would be the best time to run the calculation.
Are you in a specialty phase of a plan?
Great work. In my experience, level 9.0 sweet spot is doable with a correctly set FTP, especially with longer workout. The threshold zone is calibrated differently. For example a level 7.5 threshold is more difficult than a 9.0 SS.
this doesn’t mean your FTP isn’t set a bit low, though. Looks like you had even more in the tank.