Automatic retry in case of routing server failures

[AlanOfTheBerg]

I've seen routing pop-up on the screen from a request I submitted several minutes before. I'm not sure of the parameters for how/why this happens.

[cobra]

And then waze hangs... I was running a route, and took an off route turn. Waze tried to re-route but timed out. Then waze is kind of confused. It shows a turn which I missed as the next turn, but no route (purple) road line. After a while it froze and stopped updating.

[sdschramm]

I was about to open a new thread asking if anyone else was having these issues, but apparently I'm not the only one! I too get the time outs over 75% of the time. Very annoying! In fact lately I hesitate to even launch the app due to it not working most of the time, not to mention being bombarded with annoying pop-ups that can not be disabled! I really hope there is an update to fix this ASAP!!!

iPhone 4
iOS 5.0.1 and now 5.1.1
AT&T and WiFi
Philadelphia and King of Prussia area
Waze 3.2.0.0

[erik9999]

I have reverted to TomTom. Kind of embarrased by all the people I raved to, telling me this is a major issue for them as well. Fix it. Can it be fixed?

[Extski]

I have also noticed this. Prior to the current iPhone app version I had no failures with the initial route or with "alternate routes". Ever since the app was updated, it fails about 2/3 of the time. Very frustrating.

Mine is now working well again. Maybe the Waze app update fixed it or the server was fixed. Thanks!

[AlanOfTheBerg]

The routing working is up and down. I've had it work fine for 20 minutes, keeping up with changes/off route just fine, then be dead again and as I go off route, it doesn't recalc. Really inconsistent this entire week.

[CBenson]

The routing working is up and down. I've had it work fine for 20 minutes, keeping up with changes/off route just fine, then be dead again and as I go off route, it doesn't recalc. Really inconsistent this entire week.

The inability to recalculate when I go offroute and the inability to get a route from the server seem to be independent problems for me. Most of the time when waze doesn't reroute when I go off route, if I ask for a new route waze will give it to me just fine, it just doesn't do it automatically. So from where I sit it doesn't look like the failure to recalculate when you go off route is directly related to the sever timeout problems.

[gettingthere]

Although I have seen Waze fail to reroute when I don't have a server connection. So it could also be related to the new logic that Waze put into the client regarding routing. Could be that there is a bug that occurs in certain situations where Waze does not try request a re-route.

If it was a server issue the Waze client would request a new route but then time out.

[AlanOfTheBerg]

The inability to recalculate when I go offroute and the inability to get a route from the server seem to be independent problems for me. Most of the time when waze doesn't reroute when I go off route, if I ask for a new route waze will give it to me just fine, it just doesn't do it automatically. So from where I sit it doesn't look like the failure to recalculate when you go off route is directly related to the sever timeout problems.

Me, too, but it is unclear if this is using client-side routing. We really have no way to tell if the client couldn't contact the server and created the route itself.

What's also odd about this is I captured video and mentioned specifically in a pre-3.2 beta, that I could take my phone offline and the client would recalc the route automatically. (Offline here means no data; Waze showed no connection.) So, why I think these are related is that when the app shows that it cannot connect to the server, it seems to recalc just fine, but when the routing servers are loaded and having issues, like the last two weeks, they are still "contactable" or pingable, but Waze is unable to get any routing response from them often. I feel this is causing some of the behavior we are seeing.