@Brian-McG I thought you might find this interesting. I got out to test executing the route using my new Garmin Zumo XT3. Like MRA at waypoint#7, the XT3 recognized that the actual road did not match the HERE generated route. Zumo XT's have an Off-Route Recalculation option that essentially stops routing until the route rejoins the actual road, which it did further up where the road straightened out. The route re-started automatically with no intervention required on my part.
At the same time (side-by-side), I executed the route using the MRA Phone app. I had been playing with Nav Functional settings on the app to try to correct the "turn around" behavior from my first attempt. I enabled the "Skip Waypoints automatically" hoping it would ignore WP#7 and continue onward to WP#8 as it normally would. Well, that didn't work like I thought it would. The skip didn't kick in immediately. It wasn't until I was almost on top of WP#8 before I got a message, and then when I passed WP#8, the app tried to turn me around back to it. It was getting unworkable, so I stopped the route on the app altogther.
I'm going to change things up on the app again to try to get a successful run through that segment:
Switch to "Offline Navigation" from Online -- I don't know if this will change any behavior, but it's worth it to see if anything changes.
"Skip Waypoints automatically" turned OFF -- Maybe a manual skip when the problem with WP#7 first appears will give me a clean path to waypoint#8.
"Automatic recalculations" -- I was considering turning that option ON, but my fear is that it will trigger MRA trying to turn me around. If all else fails, maybe I change that on a subsequent attempt.
When getting ready to start the route on the app, it's clear that that it knows ahead of time about the issue:
[image: 1783791877802-screenshot-2026-07-11-at-9.52.41-am.png]
It looks like it has already decided to turn around at WP#7, and double back counterclockwise to the main road (Kanan Road) to reach WP#8. That's not what I want, but....