Last week I encountered a confusing behaviour of MFN. I started a tour with about 20 waypoints, the route was calculated and I followed the instructions. After a while (maybe 10 minutes) MFN told me "recalculating the route” and then "route not found” and stopped navigation. In "route info” – "itinerary” there were "no manoeuvres”.
It took me some time to realize it must have to do with HD traffic. HD traffic info is not present directly after application start, it only appears after a certain time. So these informations are not present if driving begins immediately after starting the app.
I had to deselect one waypoint after the other until I found out that two of the waypoints were on a temporary blocked road. Only then I could change the route.
This approach is rather impractical, at least I would expect that MFN explains which waypoint causes the route not found-message in the form of "waypoint 5 closed” or whatever.
It took me some time to realize it must have to do with HD traffic. HD traffic info is not present directly after application start, it only appears after a certain time. So these informations are not present if driving begins immediately after starting the app.
I had to deselect one waypoint after the other until I found out that two of the waypoints were on a temporary blocked road. Only then I could change the route.
This approach is rather impractical, at least I would expect that MFN explains which waypoint causes the route not found-message in the form of "waypoint 5 closed” or whatever.