Autoskip not triggered

[Makro]

Today I was driving a route, where part of the route turned out to be closed because of some construction work. So I drove around it, and the myrouteapp was trying to get me back on the planned route, just as it should.

For some reason it didn't want to auto skip a shaping point, part of the planned route, that obviously wasn't relevant anymore.

I ignored the app's desire to get me to routepoint 10, and continued the route. Then it wanted me to turn around to go to routepoint 10.
I had to skip the waypoint manually (in the menu), to convince the app not to go back.

Skip waypoints automatically was enabled during the ride.

[Con Hennekens]

@Makro, a waypoint will not be skipped until the third recalculation, and then only if it is NOT the most nearby waypoint along the route. It is clear that in your specific situation this is not the most desirable method, but it is a trade-off between skipping too soon (on a route that was meticulously planned!) and skipping too late like in this case. Therefore we have the manual skipping feature

I am quite sure, when you would not have skipped manually, at the first occasion it would have been skipped automatically.

[Makro]

@Con-Hennekens
Con, I understand the reasoning.

I don't know the implemented algorithms, so the following may not be worth much. But I'd like to help as much as possible, so I will be thinking out loud for inspiration to improve it...

This situation occurred because of a route deviation, where the app was forced to recalculate, in order to get back on the planned route.
This recalculation could take additional factors into consideration.

If there's any waypoints between the current location (where recalculation takes place) and the location where the planned route is reached, then:
-waypoints between the location deviated from the original route, and where the planned route is reached, must be skipped.
-From the location where the original route is reached, the next x waypoints must be examined: if there's any going back and forth at the same street, not present in the original route, then remove the waypoints causing this.

I hope it helps

[Con Hennekens]

@Makro, especially the first rule would lead to undesired skipping of many waypoints, especially if you consider that many routes are starting and ending at (approximately) the same place. It is still a trade-off Ideas are always welcome, but rest assured that many rulesets have been tried already.

[Makro]

@Con-Hennekens
As long as Garmin does this better we have to do something
I have seen many weird things on my Garmin, like recalculating several times within a very short time, but not this.

The first rule can be done, but it has to take waypoint numbering into consideration. I didnt intend to describe the entire algorithm, but to give ideas.
Anyway, lets leave it to the developers to consider.

[Con Hennekens]

@Makro, What I remember from my Zumo 660 and 390 is that there really was no logic at autoskip at all. If you missed a point, it simple went to the next, not considering anything. Maybe if you are used to that, you consider that to be better, but I personally don't. I don't know though if things got better on the newer Zumo's. Maybe you can tell the logic behind the XT skipping waypoints?

The philosophy behind the skipping algorithm is that you want to ride as much of the route as possible. Hence it does not immediately skip at the first occasion.