9 Days out from a new AI FTP detection. Currently on a rest week.
I rode to work in the morning, 40 minutes easy. This got automatically linked with the planned 1:30hr endurance ride on my calendar. Unlinking the ride (planning to do this endurance ride) results in a 14W or 4% increase in the FTP prediction. Surely something is wrong here.
Just flagging as a potential bug to help iron out these issues.
Curious, did you ever put in the RPE for the commute ride? (before or after the screenshots?)
Also does it seem to you your HR was very low for the power during steady sections of ride? I often have garmin issues with Vo2max when I go and do a shorter run 6-10km strong aerobic easy run (a bit slower than Marathon pace) when it’s cool out early in the morning… it will freak out and give me a high vo2max because of the higher pace and a low HR… (no HR drift yet cuz short run, cool out, early AM low HR). BUT… I don’t think TR uses HR so heavily… but idk
Never entered RPE. The HR seems fairly normal for me. The only change was unlinking the ride from the planned endurance ride. If I link it again, it drops back down to 347.
Hey @MattM 
First and foremost, I want to explain there is a bug with plans that are set to Outside.
More info here:
That said, what probably happened here is that, when the ride got matched to the scheduled TR Workout, AI FTP Prediction thought you completed just that workout and the ride data within it, so for that day you only did just that training.
Unmatching the workout told AI FTP Prediction that you were going to also complete the scheduled Endurance TR Workout so now that extra workout was added to the prediction. If you unmatch the workout today (which I would recommend, because you didn’t follow it and rode unstructured) you’ll likely see your FTP stay the same (347), as yesterday has passed, and AI FTP Prediction knows you didn’t complete the scheduled Endurance workouts from yesterday.
Hope that makes sense!
