On the specific point of why did it skip and ignored the skip waypoints turned off, I can't answer. The result does make sense if you hadn't disabled the skipping though, so I think the only fault/bug is the skip flag not working
From a 'logic' point of view looking at the map (as a routing machine rather than a human) you can see that 18 is the closest future point on the route to 14. 15 is a long way down.
As Marinus suggests, the problem may be from using OpenStreetMap (OSM) on the app. You're used one routing engine (OSM router) to build the route and then asking another one (HERE router used by MRA app) to navigate. The two often don't agree.
At risk of 'teaching grandma to suck eggs' it's worth comparing the two routes in the planner before setting off (Toolkit -> Compare route with...). Then, if you don't like where HERE is actually going to take you, you can add some extra waypoints to make HERE follow the OSM route.
My personal experience is that OSM often routes as though you were cycling - it favours smaller roads, which can be entertaining, but occasionally you get the surprise of a tiny track, etc.
114376
022689
0561
07477
0219
