Moderators: support, The Fej, Unholy, krankyd
by mrbedrock » Thu Aug 02, 2012 11:15 am
I seem to get routing timeouts when the route that needs to be calculated is over 200km distance at all times, wherever I am. Seems like the timeout trigger in the application is set too short and needs to allow some more time in order for the routing server to return the (long) calculated route.
Wazing on Samsung Galaxy S2

-
mrbedrock
-
- Posts: 4
- Joined: Thu May 24, 2012 12:42 pm
- Location: Sofia, Bulgaria
- Has thanked: 0 time
- Been thanked: 0 time
by otyyys » Sat Feb 18, 2012 5:23 pm
I had the same problem in past few days. Practicaly imposible to find route due to "oh oh" "routing server timeout". I was near Jihlava in Czech republic.
-
otyyys
-
- Posts: 1
- Joined: Wed Dec 07, 2011 8:42 pm
- Has thanked: 0 time
- Been thanked: 0 time
by PAULROLLASON » Wed Feb 29, 2012 10:03 pm
I`ve had this problem for about 4-5 days but after 10 miles or so it normally finds a route - but today i travelled from Birmingham to south Wales in the U.K. and it took over 120 miles plus and over 40+ attempts to get a route - just kept getting route server error/timeout message every time - also my points have not been added for about 3 days - don`t know if thats connected...
-
PAULROLLASON
-
- Posts: 2
- Joined: Wed Dec 07, 2011 7:05 am
- Has thanked: 0 time
- Been thanked: 0 time
by robin1979 » Mon Aug 06, 2012 11:02 am
gerben wrote:abernaert wrote:OK, will try to report all timeout errors.
Know a good site for timezones?
I'm not sure what my time difference with GMT is.
We are in CET, which is GMT+1
Summertime is GMT+2

MapSquadEurope
Area Manager - Europe
-
robin1979
- Waze Champs
-
- Posts: 2964
- Joined: Thu Sep 10, 2009 6:49 am
- Location: EUROPE
- Has thanked: 2 times
- Been thanked: 13 times
Return to Website, Community, General
Who is online
Users browsing this forum: Google Feedfetcher