For some reason, the only suggestion I have is Rest Day…every day.
I have a race in my calendar. I’m running 17.26. Resetting my watch didn’t change it.
For some reason, the only suggestion I have is Rest Day…every day.
I have a race in my calendar. I’m running 17.26. Resetting my watch didn’t change it.
All
We are aware of this disruption and have a fix coming soon. As some of you have already seen, you can change a setting, such as your Heart Rate/Power Zones to manually trigger a new changelog to get…
All,
This should be fixed for most users. If you are still experiencing this, please attempt the workaround I mentioned and let us know if the issue still persists by creating a new post.
I had support open a technical case for it this morning as well. Seeing the same thing here. I tried resetting my watch, and changing the priority of races, all to no avail. Something is bad in 17.26.…
Should bring it to their attention more, yeah.
Can you email to [email protected]
Thanks for the update. Hopefully resolved quickly. Only started as an issue for me today and thankfully the workaround has helped but certainly not a long term solution!
All
We are aware of this disruption and have a fix coming soon. As some of you have already seen, you can change a setting, such as your Heart Rate/Power Zones to manually trigger a new changelog to get added to your sync queue which will resolve this. For example, you could change the zones by 1 BPM or what the Zones are set by (i.e. % of Max to % of LT), and then change it back. You can also wait for the full fix to be released if you wish.
I will update this thread when the fix is released.
I tried the workaround you suggested, but didn't worked.
This issue is compromising our trainings, we hope it will be fixed soon.
All of a sudden, today the training suggestions started working regularly again. The problems related to abnormal heart rate spikes also seem to have disappeared
All,
This should be fixed for most users. If you are still experiencing this, please attempt the workaround I mentioned and let us know if the issue still persists by creating a new post.