As far as long distance routing, and before the thread gets off on the wrong foot. I get it and understand what you mean, however that is not at all what I am referring to in my problem that I am trying to report and share. See, I am well below 200 miles left. In that, it is approx. 200 miles between Des Moines and KC anyways. So we are under the known limit. But what is unknown is the true limit in the NA server. I can right now get a route from here in KC to Surprise, AZ, 1500 miles on my phone right now, door to door, turn by turn. It isn't the most optimum route, but for this setup, it sure is one nice option if I ever planned to make that trek. I understand that in the world server there are limits of 200 miles for routing, but I distinctly remember that they raised that here in the NA server.
So I don't want this thread to get hung up on that thought process. What the true problem is, is that there seems to be a problem with the routing server and the device when they communicate with each other, something I don't know. My best assumption is that the tiles as you go along and are reporting back to Waze aren't matching completely, hence why the magenta route line ends shortly before me approaching it, and doesn't continue on the remaining 140 miles.
Also, in my observations of this since the latest versions through beta and market versions, it only seems to occur on long stretches of freeway, where there are minimal junctions/nodes and there is substantial distances between the next node/ramps. Case in point is on a similar distanced trek, but I took it across the back country highways through Missouri. Yeah, there were some errors along the way, I planned weeks before, checking routing, and updating the map along the route I was going to take. The map updated with all of the correct routing, but it wanted to take a route it thought was faster until I hit a point that it just continued on the way that it should. I get that. But I have trekked I-35 plenty with Waze and it has only been happening like the screenshots as of recent with the recent betas etc. It wasn't that way in 3.0 or 2.4 on and on.
I'm just making the observation that along the long stretch, I see this problem with the proceed to highlighted route, the thing kept recalculating every time I hit the end of the magenta line and then proceed to highlighted route. On my trek with the back country, it would take me to the next junction and try to have me go the other way until like I said, I reached a point and it said this way actually is faster and then it routed me on a continual path. I even had loss of cellular service, but because I had a route already on there and no breaks in the magenta line, I was able to navigate with it just fine. If anyone knows State Hwy 7 in Missouri, you should know what I mean between Harrisonville and Osage Beach. So again, logic has it, two scenarios, similar distances, different layouts. One with many junctions, one with very few. The one with very few is causing me problems. And by the looks of it and all the user reports along the freeways, I'm not the only one...