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

Custom workout not appearing on sub sport categories (v16.17)

Since update 16.17 my custom workouts are only visible on base sport categories (e.g. running, cycling). They are not visible on the related sub sport categories (e.g. trail running, road cycling etc.).

This used to work in previous version 4.19 and stopped working in 16.17.

A viable workaround is using the „Training“ sport categorie (all custom trainings show up there) and from there selecting the desired sport categorie. Drawback: You have to use the same datafields and layout for all sport categories.

Most likely same problem as: https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series/345924/custom-workout-not-appearing

  • A viable workaround is using the „Training“ sport categorie (all custom trainings show up there) and from there selecting the desired sport categorie. Drawback: You have to use the same datafields and layout for all sport categories.

    I tried this on my 955 with the "Workouts" app (my watch's language is English), and I don't see the same drawback you're seeing. In the app, I can select any workout I want (as you said.) Then the app gives me option of selecting any profile associated with the workout's main sport - e.g. if I pick a Run workout, then I can select any profile related to running (e.g. Run, Track Run, Treadmill, etc.) When I pick a profile, I get the datafields and layouts associated with that profile. (Each of my run profiles has different datafields/layouts and settings.)

  • You are completly right regarding the workaround. My „Workouts“ app behaves exactly as you describe. I was wrong (don‘t know why).

    But what would be interesting if the beforehand problem „Custom workout not appearing on sub sport categories“ occurs on your 965 too?

  • Yes, it also happens on my 955. I'm guessing everyone on the "unified' firmware for 955/965/Fenix 7/Epix gen 2/whatever is seeing the same problem. Or at least it's happening for both 955 and 965, anyway.

  • Ah! I just posted a similar question... I assumed it was a Forerunner 965 thing (I just moved from a Fenix) and not a firmware thing. Firmware makes more sense - I thought I was going crazy.