is anyone else experiencing an unusual slow AI service currently? Over the past weeks, the prediction and workout selection were usually done rather quickly, especially during European daytime and a little slower once the Americans seemingly also started waking up and training (late evening in central Europe).
However, right now I was waiting for minutes for the UI in the app to even start the progress bar for the prediction or figure out what today’s workout should be after I modified it from a dynamic endurance of up to 2h to a static one of 90min. Given that it’s my last workout before the prediction window ends on Saturday, there shouldn’t be that much to calculate for either.
Unfortunately can’t provide a screenshot anymore, but you’d have seen the loading animation for the workout and the empty progress bar for the prediction. In the calendar it would have been all future workouts and the prediction having their default loading animation
I had the same happen the other day. I did a workout that I rated Max Effort due to Intensity and it (thankfully!) lowered my predicted AIFTP, but it took a very long time for the update to finish. I finally quit the app and went back in and it was all complete. I feel like things happen fast on the back end but every once in a while it seems to get stuck in the app visual.
Out of curiosity, what kind of device were you using when this happened? Also something from Apple?
I’m starting to wonder if there’s something like request throttling happening unintentionally with the TR app, which e.g. some browsers do automatically if they detect a tab to no longer be in-focus.
Or the TR app simply lacks any means to update automatically client-side if a pushed update from the server got lost. You can see this in a unrelated and not very relevant scenario where you make changes to your calendar affecting the prediction on another device or via the browser and the app will never automatically receive this update without a user interaction (switching views or restarting the app), which can be a bit annoying on iOS, as apps tend to just keep running in the background after switching to another app and don’t restart when opened again later.
Just wanted to update this thread as it looks to be the issue below:
Apple recently required us to make some changes on our end, and it’s looking like those updates have caused some unexpected errors for certain athletes on Apple devices. It got flagged as high priority and we’re on it.
In the meantime, restarting the app has worked as a temporary workaround for some athletes, so that’s worth a try if you haven’t already.
To help us track down exactly what’s going wrong, we’ve also put together a beta build with extra logging. You don’t have to do this as it won’t solve the problem you’re running into, but if you can, it’ll give us better visibility into what’s happening behind the scenes and help us get a proper fix out quicker if anyone is willing to try it.
If you’re up for it, here’s how to install it:
On your iPhone or iPad, install theTestFlight appfrom the App Store if you don’t have it already.
Tap Accept, then Install to download the TrainerRoad beta build.
Open the beta version of TrainerRoad and use it as you normally would.
From there, see if the same issue still pops up on the beta version. If it does, leave the app open for a bit afterwards so the logs have time to sync over to us, then let us know and we’ll dig in from there.
Also shout out to @martenk who’s sent very helpful info
@Caro.Gomez-Villafane - not sure if this helps, but I had about a 60 second wait for the app to update my prediction after my workout this morning. It was the first workout after accepting a detection, so it might be that, but sharing if they want to look at the logs. First workout since installing the beta.
