Garmin Fenix 7 and Epix Lose Turn-by-Turn Navigation After Platform Bug

Garmin's premium watches have a navigation problem right now. A platform-side bug in Garmin Connect is silently killing Turn-by-Turn (TBT) alerts on the Fenix 7, Epix Gen 2, and Forerunner 955 for courses synced from Komoot or Strava. If you loaded a route this week and got zero cues on your wrist, this is why.

What Is Actually Breaking

The issue sits in Garmin Connect's course processing pipeline, not in the watch firmware itself. When you sync a route from Komoot or Strava into Garmin Connect and push it to your device, the platform is failing to embed the TBT cue data correctly into the exported file. The watch receives the GPS breadcrumb line just fine, so you still get the purple route drawn on the map. What disappears are the directional alerts, the vibration and arrow pop-up telling you to turn left in 200 meters. Two completely separate data layers, and only one is broken.

This matters more than a minor inconvenience. Fenix 7 and Epix retail between 700 and 1000 euros depending on the variant. The Forerunner 955 sits around 500 euros. At those price points, reliable navigation is a core promise, not a bonus feature. Coros Vertix 2S and Polar Grit X2 Pro both handle route cues natively from their own platforms without this kind of third-party sync dependency breaking things.

The Manual FIT File Workaround

The fastest fix right now is bypassing Garmin Connect's sync entirely. Export your route directly from Komoot or Strava as a FIT file with embedded cue points. Then connect your watch via USB or the watch's mass storage mode and drop the FIT file directly into the GARMIN/NewFiles folder on the device. The watch reads the cue data straight from the file, skipping the broken Connect processing step entirely. Reboot the watch after the transfer to make sure it indexes correctly.

Alternatively, if you built the course inside Garmin Connect's own course builder tool, the TBT cues appear to survive intact in most reported cases. The failure rate is highest specifically on routes imported from third-party platforms. Worth knowing if you need a quick workaround tonight before a long ride.

Who Gets Hit Hardest

Triathletes and cyclists doing unfamiliar sportive routes are the obvious victims here. A 140-kilometer bike leg with 60 cue points and zero alerts is a safety issue, not just an inconvenience. Runners using Komoot for trail navigation take a hit too, especially on technical single-track where missing a junction costs real time. Hyrox and CrossFit athletes generally are not affected since they are not routing workouts, but any endurance athlete who relies on Strava route planning and syncs to a Fenix or Epix should check their setup before their next long session.

Apple Watch Ultra 2 handles this differently by leaning on iPhone-side processing and Apple Maps integration, which sidesteps the Garmin Connect bottleneck entirely, though it trades battery life (18 hours versus 57 hours on Fenix 7 Solar) to do it. Whoop 5.0 has no GPS or navigation at all, so not relevant here. Coros' own platform handles route cues entirely on-device after initial sync, which has kept it clean in this specific failure mode.

What Garmin Has Not Said Yet

As of this writing, Garmin has not issued a public statement or a firmware fix. No timeline has been confirmed. The bug appears to have surfaced within the last two weeks based on community reports on the Garmin forums and Reddit's r/Garmin. Given that this is a server-side platform issue rather than a firmware bug, Garmin could theoretically push a fix without requiring a watch update, which would speed resolution. But silence from Garmin on a navigation failure affecting their flagship lineup is frustrating regardless of the fix timeline.

What is also missing from Garmin's response is any acknowledgment of the scope. This affects three major watch lines simultaneously. The Fenix 7 series alone has multiple hardware variants across solar and sapphire editions. A coordinated communication to affected users via the Connect app would cost Garmin nothing and would go a long way.

Use the FIT file workaround until Garmin patches the Connect pipeline. It takes about three minutes to set up and works reliably. If you are buying right now and navigation accuracy is non-negotiable, the Coros Vertix 2S at around 699 euros is worth a serious look as an alternative, especially for cycling. Garmin's ecosystem is deeper overall, but right now their platform is the weak link.