Training Status stuck for over a week at 530 load and maintaining
Thank you for your participation in this forum thread. So that I may assist you further, please reply with the following:
We believe that we have a fix for this report that will be rolling out with the next software release for this device. While I do not have a timetable for this release, I will be updating this thread…
We have released a public beta to resolve this issue. Please see: Enrolling in Garmin Beta Software Program on how to enroll in the public beta to receive the fix.
If you are experiencing this issue…
Garmin please give us a timeline on fixing this issue. It seems to be universal for almost all 955 owners. Is this going to be fixed in 48 to 72 hours or are we going to be dealing with this for months…
I am having the same problems. My watch is showing the training status on my watch but the acute load has not changed in a few weeks. Sticks at 841 no matter what. On Garmin Connect the it is showing that…
My watch just noticed me about relaxing.. :D So I think he got me there. But yes, seen in other threads also, he seems to be very fixated to one thing and ignores that how can the 945 and Edge 530 give me status (and all the runs are btw done with 955, but the 955 itself can't).
just doing a proper cause/effect verification. If you would have spent 5 years + doing level 1/2/3 support you would understand. The amount of time i’ve lost investigating a trail because someone said something and I didn’t validate. Now garmin dev can use this user problem and use it to nail down the issue ;)
we have to remember that the issue is circunstancial. There's something different between his watch use case and someone else use case which trigger the issue. By blaming Garmin all days we are not helping solve the problem. It's by doing trial and error and eliminating possibility that we can help a lot.
So what would you suggest me to try? I kind of have no ideas, as 945/Edge 530 get statuses from activities done in 955 via TrueUp, but the 955 itself doesn't.
And not really loving the idea of doing factory reset as there's no reason to assume this wouldn't happen again.