''Couldn't reach way point 61 due to search timeout''
I am passing 66 waypoints (all in one city) with ;sort to get optimized route. But 6 coordinates cause this issue. If I remove those 6 coordinates I get route. But interesting part is that if I use those 6 coordinates with few other (less then 15-20) other coordinates it also returns route. But if I use at least one of those 6 with all others it get's me this issue. Also all coordinates are real, close to road, real addresses. Anyone had similar experience or does anyone have some tips or solution to this problem?
url:
Since you are using the sort mode in Fleet Telematics API normal calculate route request, there is a timeout of 50 - 60 sec. Also you are using upto 90 waypoint in sort mode, which is quite expensive computation wise with the strict timeout. So it could be expected that the calculation hits the timeout.
Please use Waypoint Sequence Extension API, which has higher timeout and a different algorithm.