Navigation completely ignoring a turn.

I've run into things like this since staring using Edge devices 13 years ago. I chalk it up to errors/discrepancies between the map used to lay out the course and the map in the Edge.  For Nav, the Edge takes the track points from the course, matches them up with it's map as best as it can, and generates Nav based on the result.  There's a number of things that can go wrong, road coordinates, road properties, intersection coordinates, intersection properties...   It used to be much more prevalent than it is nowadays, which I assume is due to improved map data all the way around.

I occasionally see this on car sat navs too (built in, goggle maps etc).  I think it happens when the priority at the junction is not correct in the database so as far as the nav is concerned you are simply following the road rather than making a turn.

So, you have an issue with a particular intersection but don’t say what particular intersection. That might be useful to know. 

If it helps, it’s the intersection of Pilot Grove Road and Bierman Road in Dubuque County Iowa. Headed west on pilot Grove turning north on Bierman.

can you help now that you have that info?

You indicated that it happened at a particular intersection. That's a strong indication that the issue is particular to that particular intersection. So, yeah, you should have provided that info upfront.

What are you using to plan the route? What map are you using to plan the route?

I’ve built routes via RWGPS and garmin connect. Both have the issue. Seems like it’s linked to map that is on the unit somehow.

The maps on the device is based on Openstreetmap (OSM). The route planners let you use OSM maps for planning.

You'll generally get better results with using OSM maps to plan the route.

RWGPS defaults to using Google maps for routing and the routing info with that map for this intersection is a bit odd.

Not announcing the turn here is weird. Even with the odd routing info, I would have expected the turn to be announced.

I'd suggest selecting OSM and have RWGPS or Connect recreate the course through the intersection.

---------------------------------------------------

The Edges are just using the track information in the file.

They create the "turn guidance" (the big white arrows) by "walking" the track to figure out what roads or paths the track appears to follow.

It doesn't really matter what course planner you use. They all do the same thing. The map you use for planning can be an issue.

The Edges can handle some degree of difference for the track and the roads/paths on the installed maps but they can still get confused.

The OSM data for the intersection is correct.

Bierman road wasn't quite placed correctly north of the intersection but that shouldn't have had anything to do with your issue (I fixed it anyway).

Keep in mind that OSM might not always be accurate for such rural areas.

This intersection isn't complicated. So, I'm surprised you had an issue.

The other one I can recall having an issue with isn’t complicated either. That one is a T intersection where I’m turning.