- July 21, 2020 at 12:55 am #8251
I have the following setup :
– Apple Watch (latest version)
– Stryd App
– Training Peaks Premium
– 80/20 10K Power Plan
Not sure if more a TP/Stryd problem and if I should rather ask on their forum but let me try to ask here first…
Whenever I update my power threshold and “run” zones in Training Peaks, I can immediately see the effect applied on next planned workouts. Checking the Workout Details, the power range is matching the target zones.
Also the Stryd app on my watch is definitely able to fetch latest workout updates… Whenever I create a new planned workout in TP, I can immediately get it when triggering a fetch from the app.
However, when running with the workout, the power zones are incorrect. They are not matching the workout details in TP. Not sure exactly which zones I am getting… I may be tempted to say it does match old zones but I do not fully remember.
Do you see what is going wrong here ? and how I can ensure that downloaded workout on the Stryd app always match the workout details ?
SylvainJuly 21, 2020 at 9:35 am #8252
I see this issue all the time on Garmin devices, and I believe that the fix would be the same for Stryd devices. The root cause is that a change in threshold does not trigger a new sync to 3rd party devices. Only a complete change in the daily workout that contains that new threshold.
To fix that, see our document Understanding Your TrainingPeaks Structured Workout Plan but I have included the relevant section below for your convenience:
Q: My thresholds recently changed, and I updated my 80/20 zones in TrainingPeaks using the instructions in this document. The workouts on my device still display the old zones. Why?
A: Depending on the device, TrainingPeaks will sync up to several weeks of workouts at a time to Garmin Connect, Zwift, or Wahoo. Those workouts contain your custom 80/20 zones at the time the sync took place. Updating zones in TrainingPeaks does not trigger a new sync, so the old zones remain on your device. To force a new sync, the workouts must be removed and re-added using one of the following methods:
– Use the Shift feature in the TrainingPeaks calendar (click on the triple horizontal lines found by hovering over a given day or week in the calendar and choose Shift) and shift your plan from today forward by one week. Wait for that change to reflect in the 3rd party calendar, then shift the workouts back to their original dates in TrainingPeaks.
– Cut a given workout(s) off of the calendar, wait for that change to reflect in the 3rd party calendar, then paste the workouts back to their original dates in TrainingPeaks.
– Unapply the entire plan in TrainingPeaks, wait for that change to reflect in the 3rd party calendar, then reapply the entire plan.
These actions lead TrainingPeaks to consider the affected workouts to be “new” workouts and force a re-sync to the 3rd party, which then sends your updated zones to your device.
DavidJuly 21, 2020 at 10:07 pm #8254
Thanks a lot David,
I will try your suggestion for my next run and let you know.
Also has the behavior you describe already reported as a bug to Training Peaks ?
SylvainJuly 22, 2020 at 12:02 pm #8256
TP does not consider it a bug. The entire workout is sent as a package, and the zones are included within that package. Garmin does not have an API to receive a zone-only package update, they only allow for a the entire workout(s) to be sent. TP could not fix it if they wanted to.July 24, 2020 at 12:17 am #8260
I tried some of the suggested workarounds (temporary shifting the plan, and unapply/reapply the plan) unfortunately it did not work. Also when I reapplied the plan, it created duplicated for all past planned workouts already executed, I had to manually delete them 🙁
Also I kindly disagree about your feedback on this limitation… Maybe not a “bug” strictly speaking but that should be quite an easy to handle if properly coordinated between the 3rd party and TP API.
There is not really a need to expose a “zone-only” package update but just kind of “last time the workout was modified whatever the change” timestamp. From there, the 3rd party can easily check if there is a need to re-download the full package or not (that is a pretty standard programming pattern in such a case). As I have the problem on Stryd app on iWatch and you mention you encounter the same on Garmin, I guess the limitation (if not a bug) is located on TP API.
I will try to contact Stryd support to get their perspective about that. Thanks anyway for your help.
Regards.July 24, 2020 at 4:49 pm #8261
Sylvain, I’m sorry that did not work, and particularly sorry that it doubled up your plan. That’s why we have the step “wait for the change to sync in your 3rd party calendar” to ensure that the calendar is clear before you reapply so that is does not duplicate. Strange that the calendar would be clear and then come back with twice the workouts.
Yes, stryd is the next step and I’d like to know what they say.
Your feedback about the API is good, please consider conveying it to TP, as the more complaints they get the more likely it is to be addressed.
DavidJuly 24, 2020 at 8:58 pm #8262
re. the step to wait for the change to sync. I confirm I did that (I waited for the workout to disappear from the Stryd app before making the next step). But to clarify, I meant the TP calendar. Any planned/past workout already associated with a real workout had been duplicate when I re-apply the plan. But it is OK, I only started a few days ago.
I will let you know stryd support feedback.
- You must be logged in to reply to this topic.