This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Blue triangle reboot when trying to access suggested workout from calendar widget 7.20

I successfully started a suggested workout from the calendar widget two days ago, however, today when I attempt to start a suggested work out from the calendar widget the watch blue triangle reboots every time. I am still able to successfully access the suggested work out from the run activity menu. Anyone else having this issue?

Top Replies

PedroF over 3 years ago +1

Hi, I opened a thread about this issue in the bug report section of the forum:

https://forums.garmin.com/developer/connect-iq/i/bug-reports/crash-and-reboot-when-trying-to-access-suggested-workout-after…

All Replies

0 PedroF over 3 years ago in reply to Garmin-Brooks

Hi,

I currently cannot reproduce the issue since now I am following a Garmin Coach training plan so there are not daily suggested workouts.

Mine is a Foreruner 245 (not music version). I am not having issues with the workouts from garmin coach, it occurred only with the suggested workouts.

0 rollthebones62 over 3 years ago in reply to Garmin-Brooks

I'm having the blue triangle issue and have copied the folders as you asked. I'm awaiting further instructions. Thanks!

0 rollthebones62 over 3 years ago in reply to rollthebones62

I forgot to mention that I'm using a Garmin245 non-music. This happens when trying to access the suggested workout from the widgets menu. Accessing it directly from the running menu (as another user suggested) does not cause a reboot.

0 renelentino over 3 years ago in reply to Garmin-Brooks

I have the same issue.

If I try to have a look on the suggested workout through the calendar widget it crashes. But also corrupts all sleep data.

How can I upload my Debug folder?

0 MD over 3 years ago

Has anyone any idea whether this is (supposed to be) fixed with latest beta 8.02 ? (or even 7.80 - haven't tried again since this one)

0 peterdb over 3 years ago in reply to MD

I have installed 8.02 yesterday. The issue is still there.

0 spike over 3 years ago in reply to peterdb

current beta version 8.09 (or next official firmware version) suppose to fix this according to its change log.

0 dsmith42 over 3 years ago in reply to spike

Finally. Thanks for the heads up.