I had a similar experience yesterday. Finished Kaweah, which I rated ‘Hard’ in the afternoon, and the app suggested no changes. Later in the evening the website suggested I change next Saturday’s Mount Goode to Mount Hayes. Even when I refreshed the app there were no changes suggested.
I accepted the recommendation.
Lately I have finished workouts using the Windows app and got no adaptation recommendations. Later, on the website, I got recommendations and a subsequent yellow day. Adaptions were 4 and 6 weeks out and very small, only changing TSS by 1 point in one case, and only changing IF by 0.01 in another. Nothing wrong with these, just mighty tiny and relatively far out.
@eddie Re-opening an old thread. Website on my home computer (Mac) wants me to do Antelope +2 (sweet spot 5.9) tomorrow, app wants Copper (sweet spot 5.3). Website on work computer (Windows) is good with Copper. My career PL is 5.2.
I’ve just signed up for TrainerRoad. Liking it so far, but I seem to have the same issue as mentioned here regarding adaptive changes. The website shows I have adaptions pending, but the apps (iOS & Mac) show “No Adaptions Required”. Am I doing something wrong?
It seems like the app might be running slowly on your end. The web is the best source of truth, so if the app doesn’t reflect what you’re seeing there, you might be having syncing issues with the app.
I’d recommend closing out of any other open apps and leaving the TR app open for a few minutes with a solid wifi connection to see if things sync over.
Let me know what you find. Sorry for the trouble!!
I don’t think it’s the app being slow. The app updates almost instantly with any other changes I make from another device (such as moving workouts or changing them). It is just the adaptations on the apps that don’t appear to show.
If I had the issue on just one device, you could think it was a problem with the app on that device, or even the device itself. However, the apps on my MacBook and my iPhone do not show any adaptation required when the website does.
I have also seen in this forum that I am not alone in having this issue, which would point to a problem with the app.