Routing server timeout on long drives
Since the app seems to consistently time out looking for long drives, I would recommend allowing more back end resources be used for drives over a certain mileage or time. This might require an upgrade based on the high number of users.
Instead of having just one option, I would like to be able to choose between options since there are riskier routes for adding traffic.
I'm sure I'm not the only one with this issue since I can have perfect service on an iPhone 6S and consistently have your servers time out.
Ken
shared this idea
-
Anonymous
commented
This is annoying why is Waze not fixing this issue of long trips!! Great Navigation to use but breaking it up becomes very annoying and not useful
-
Bill s
commented
Agreed. 150 miles from NJ to Worcester is not a long drive. I have to use Google maps to figure out a route!
-
Anonymous
commented
I agree - if you’re it familiar with the route, breaking it up into smaller portions really means I’ll end up using another service for I’m going to another site to figure out what smaller drives I can break my route up into.
-
Bostonchele
commented
Agree this is always an issue. Can’t even go from NY to Boston.
-
Anonymous
commented
Yes! Breaking route into smaller sections defeat the purpose of using Waze to see the best route.