It was meant to go from 227 → 247. I logged in on mobile today and did not receive a prompt to detect my new FTP. And it did the auto detect and predicted 227 → 260 in 28 days.
The main issue is: I have a ramp test scheduled for tomorrow. If my FTP stays at 227 and I do the ramp test, the max power I would need to sustain is 306W. VS, when the prediction was meant to read 247 today, it would have been 336W.
I’ve manually set it to 247W, and the ramp test and the other scheduled workouts I’ve had have come back. But now, AI FTP detection in 28 days is disabled because I updated it manually.
Did anyone else face this? Could it be a mobile-specific bug?
Detection was meant to take place on Sunday, the 31st. It didn’t. But then I manually updated it to the predicted FTP (247). Then I did an FTP test on Monday, the 1st. And got a new FTP detected modal and accepted it.
I did, mostly because it wasn’t working. A few more details on what happened on Sunday in TR:
I opened it on mobile, and the FTP Detection modal wasn’t there so I did it manually.
Then on my computer, it detected 227, which was wrong, because that’s what it was 4 weeks ago. But I accepted it. After I did, it showed 227 → 267 in 4 weeks, and very aggressive workouts over the next 4 weeks.
So I manually adjusted it to 247 and saw the previously scheduled workouts.
And after all this, I attempted an FTP test on Zwift.