For the last 4 weeks I’d been diligently following my training plan to lock in my predicted 4% FTP increase and today is the promised day.
However, upon logging into TR I wasn’t automatically presented with the usual “AI FTP Detection” dialogue (bug #1.) On my Career page I spotted the manual “Detect my FTP” button and I clicked it to receive my 4% increase.
I updated my FTP inside Zwift (where I do all my TR workouts) and then went to do my 1h45m Endurance workout. However the power was lower than expected - it was still working off my old FTP (bug #2.) I had to “refresh” the workout inside TR to trigger a resync with Zwift and then the power was correct.
The workout had an Endurance workout level of 5.4, however upon completing it with the expected Easy RPE, my Endurance athlete level stayed at 4.8 (bug #3.) The TR app says my Endurance “initial level” is 5.7, which was the level before my FTP increase.
While none of this affects my training, it does put a damper on what’s supposed to be a relatively celebratory day. In 4 weeks’ time I’m going to postpone my AI FTP Detection to a rest day so that I don’t run into these bugs again. Hoping TR support can use this feedback to make TR an even better platform!
FWIW, updating your FTP in Zwift has nothing to do with the power issues you experienced. TR sends workouts to Zwift at fixed wattage levels, so as long as your FTP is correct in TR you’ll have the right workout interval wattage in Zwift, even if your Zwift FTP is set at 0.
The likely culprit is that thecTR workout was sent to Zwift early in your day, like before you did the FTP detection. And the workout won’t automatically be resent to Zwift after the change. (Though if the FTP detection causes an update in your plan, with a different workout scheduled for the current day, that would be sent using the new FTP.)
As for why you didn’t get the prompt to run the FTP detection when you first opened TR fir the day, that does seem like an issue.
I think they changed the trigger. Yesterday, I also didn’t get the prompt when I logged into to detect, but it was available in the career page. What also was interesting was I had a new prediction and that had my old FTP. When I detected my ftp it didn’t change the future value.
TR sending fixed workouts (or at least my old FTP and % target for each block) to Zwift makes sense. It would have sent it to Zwift on Friday and TR only updated my FTP on Saturday. Thankfully it’s relatively easy to trigger a resync, I found I can just edit the workout duration to be the same as it currently is, and it lets me “save” which forces a resync.
Just want to clarify that these are not bugs so other don’t come across this thread and get confused. The only potential bug that will try and see and reproduce is #3.
Answers from TR Support:
AI FTP Detection isn’t set to automatically update your FTP. In some cases, you’ll see a prompt when logging into the app letting you know a new detection is available. If that prompt gets dismissed or doesn’t appear, you can always manually trigger a detection.
This was not asked in the support ticket, but likely what @NigelTufnel11 is describing.
I’m going to try to reproduce this on my end and pass it along to our dev team. It does sound like there could be something off with the timing of when the system checks your Athlete Level relative to when the FTP change takes effect.
@Caro.Gomez-Villafane regarding item #3 in your post above, the issue doesn’t appear so much to be the timing of when the system checks your AL relative to when the FTP change takes effect, but that workouts are sent to Zwift before the user updates their FTP, and the updating of the FTP does not trigger the workout (which does get updated immediately in TR) to be resent to Zwift. So if the user does that day’s workout in TR everything is fine, but if they do it in Zwift it is based on the previous FTP.
There are a few posts about this issue, and all seem to be related to a workout done in Zwift on the day that an FTP update is performed.
It seems like the ‘fix’ would be to re-send the workout for the day to Zwift subsequent to an FTP update being performed by the user. (This is presuming, of course, that whatever communication between the two systems is doing can recognize that there is a difference in the details of the workout, as the name of the workout might be the same both before and after the FTP detection, and will therefore update the workout in Zwift.)
#1 is just inconsistent behaviour, arguably not a bug.
#2 could easily be solved by reuploading workouts to Zwift when an FTP change occurs. @NigelTufnel11 this is what you’re describing.
#3 is a separate bug to #2 Nigel; please see screenshot below. My “initial level” of 5.7 was at the start of the day, which then became 4.8 after the FTP bump to 232W.
Just a quick follow up on this, as I had an FTP detection today, as well as a scheduled workout.
For today, my starting FTP was 286, and my workout was Volunteer, for which the highest wattage interval was 215w. This workout was sent to Zwift at some point before I looked at TR this morning.
Subsequent to my FTP detection, TR updated my FTP to 288, and the the highest wattage interval in my workout (still Volunteer) was now 216w.
Looking at Zwift, subsequent to updating FTP in TR, the highest wattage interval was still showing as 215w. Going back to TR and changing today’s workout from Indoor to Outdoor, and then back to Indoor, appears to have forced the revised workout to Zwift, as checking it after this change showed the interval at the 216w level.
So, if there could just be something added to the Zwift transfer logic to cause the revised TR workout to replace the one already sent to Zwift on that day, I think that would solve the issue some have been having. Of course, there would also need to be caveats so that, for example, a new workout isn’t sent if the user does the FTP detection after they have already done their workout for the day.
