Daily Suggested Workouts (DSW) has disappeared on 17.20

I recently updated my watch Fenix 7 Pro from 16.22 to 17.20. On 16 everything was fine, no errors, now the DSW are gone, There are no suggestions in morning raport, when i go to workouts there is no run position, in run activity when i select workout and DSW there are only settings no suggestions. I have to restart my watch to view  DSW. Yesterday i have same situation. It very frustrating to have to restart watch every day
  • Here is the message and questions from Garmin-Cody:

    Hello,

    Apologies on the frustrations with daily suggested workouts, as this has been very frustrating for our user's and Garmin is working diligently to try and determine a solution for our users experiencing the DSW concerns.

    I would like to gather some additional information from you to submit you account to the ticket our team is investigating for the daily suggested workout issue.

    If you have already been contacted, please disregard.

    Please reply with the answers to the following info outlined below:

    When did you notice the DSW feature no longer prompting?
    If you go to the DSW schedule, does it show workouts for any days?
    What time was it when you go to open the activity app to start training? (Please also confirm time zone).
    Had you recently completed an event or training plan?
    Have the steps outlined below that are suggested in our current update resolve the issue?
    Open Garmin Connect Mobile>More>Training & Planning>Races & Events.
    Select "Find an Event"
    Select any event that comes up in a search
    Select "Add to Calendar"
    Sync the watch with Garmin Connect
    Confirm the event is showing on the Training Calendar on the watch.
    Remove the event from GCM
    Sync again
    ensure the DSW is enabled
    If rebooting resolves it even temporarily, other than starting a prompted DSW workout are you taking any other actions after the reboot? (e.g. Dismiss DSW, Entering the DSW schedule, viewing morning report, starting and/or ending another workout, etc)
    Do you allow consent for Garmin to access your account in relation to investigating this specific issue?

    I look forward to your reply.

    Cody - Garmin Forum administrator

    Garmin International - North America

    Here are my answers:

    • Firt noticed the bug after updating to 17.20 or 17.23 (not really sure)
    • I can't see the DSW when the bug is happening, if I start a run it does not appear, if I go in calendar it does not show (calendar crash).
    • In the morning 6:30 AM, Montreal time zone
    • I completed a DSW yesterday evening
    • I tried the steps Garmin-Laurie
    • Rebooting solve the issue until you do a DSW, then the bug comes back until the next reboot.
    • I allow consent.

    BTW I'm rolling back to 16.22 until this is resolved. Might also go back to Apple Watch Ultra until this is resolved. The issue has completely made wy watch unusable, my training program is now completely useless and I have a race in 8 weeks. I'm so disappointed about this.

    Thank You

  • After three months Garmin is always looking for the root cause of this issue ?

    Is it a joke !

    Regarding how many reports are made over the forums (FRx55/x65 and F7/E2), Facebook group, reddit, etc. i do not understand how one of there watches at Support could not be concerned by this issue.

  • I’ve tried everything suggested as a fix: resetting the watch, reinstalling the software via the about menu trick, creating and deleting a fake coaching program. Nothing fix the problem on the 17.23 firmware version.

    Right now we have 2 options:

    • Rebooting your watch every morning if you are on the 17.23 firmware. (Not a real solution but works temporarily).
    • Or roll back to 16,22 firmware version. I’ve done it, no more problem with the DSW. I’ve done a DSW run yesterday and this morning a new DSW appears in the morning report and in the calendar. You need to turn off automatic software update if you want to stay on this version and not use Garmin Express since it seems this will push the update to the watch even if you selected not to upgrade on the watch. I had to redo the 16.22 process once because of that.
    • here is how to rooback: forums.garmin.com/.../downgrade-to-stable-16-22---instructions

    I have contacted Garmin by chat and email about this, I’ve answered Garmin-Cody questions in a long email. I’m not loosing any more time with this, I’ll stay on 16.22 until a new firmware solving the issue is released.

  • It worked as long as I did not really do the suggested workout. So for the last few days, at least the DSW were shown in the morning report and in the calendar. But yesterday I did the DSW, and guess it: this morning the DSW is gone again. 

  • Update:

    After 9 days of waiting support reached out to me via email saying:

    "engineers are working with high prio on DSW issue, can't tell exact timing but expects update soon"

    Well I think we heared that a lot and I do have some kind of trust issues with Garmin

    Anyway - Support was not aware of (nor was there a ticket created) the bpm/pace setting which is not able to be reverted or once set not kept e.g.:

    1. you are on pace,
    2. you want to switch to bpm instead,
    3. after click,
    4. run activity still set on pace (not as expected on bpm)

    Should also behave the same when switching bpm to pace

    Anyone who is still in 17.23 can you confirm that?

    If so it may be worth creating a Thread with this issue and tell support as BUG report was closed for no reason. Slight smile

    I read of 1 or 2 people beside myself seeing that issue but I cant try again due to rollback to 16.22...

  • Maybe I got a tiny new aspect. Yesterday I executed the DSW and after sync with the app I immediately rebooted the watch. This morning everything worked as expected, with the DSW in morning report, calendar and training. I think I will continue like this in order to save me the frustration in the morning.

  • same for me, but it’s not done, common Garmin…

  • That is interesting. So the bug might be related to doing the DSW and not a fullclock cycle. Once the DSW has been done software can’t reactivate the DSW daily program. 

    ?

  • It work until next DSW is done. It’s nothing new Disappointed