I was using Waze last night on my drive back to Dallas.
When I started Waze, I was on US Hwy 77 just south of FM1624 as shown here on the map:https://www.waze.com/cartouche_old/?zoo ... FFFFFFTTTT
The fastest route back to Dallas is to take US Hwy 77 north to Waco, then pick up I-35 north into Dallas. The route that Waze generated had me go north on US Hwy 77, then turn onto State HIghway 21. I ignored the turn onto State Hwy 21 and continued north, so Waze recalculated my route. The new route that it came up with had me continue north on US Hwy 77 for just under 10 miles to Private Road 7018, where it basically had me turn around and backtrack to State HIghway 21. I'm not sure why it selected this private road to turn around on since I passed through the town of Lexington where I could have turned around, plus any number of other state and county roads off of 77 that would have allowed me to turn back. Since my intention was to continue north, I ignored this turn as well so Waze recalculated the route again. The new route had me continue north for approximately 17 miles to US Hwy 79 at Rockdale. At this intersection, the route wanted me to take the exit to Hwy 79, then turn back onto the other ramp to go south on 77 all the way back to State Highway 21. At this point, the route being given was a little over an hour longer than the normal time needed to reach my destination.
I stopped navigation from the menu, then selected my destination again to generate a new route. When the new route was generated, it matched up with my desired route that takes the correct amount of time. So the question is, when you miss a turn and Waze recalculates the route, does it work out a new route to the destination from your current location? Or does it just try to get you back the route it originally generated? I originally assumed there was a map issue that was preventing my desired route from being found which it was it wanted to use Highway 21, but when it suggested backtracking almost 30 miles and passing numerous other roads, I wasn't so sure. And since it found the correct road when I restarted navigation, it doesn't appear to be a map data issue.