Have also noticed this! Even moving one of the existing points seems to clear the flag.

Replicated here. 

In case helps: See in Public Journeys a test route ref 903914; created as paved-only for simplicity; with a Via point with Uturn allowed at the point where Ushaw Moor Station Rd crosses the Deerness Valley cycle trail. If do any of dragging the start or end points, or adding a via point at a location that should not involve the U turn (eg add Esh Village), the U-turn is lost and instead the route is continued south from the U-turn location to make a turn in a street in New Brancepeth. (An odd thing is that the automatically revised route itself involves a U-turn, as it goes in and out of a cul de sac...) 

If the route is aved with the originally specified Uturn in place, and then opened in the App and a new Via point added there, the same effect occurs; but there is no way (SFAIAA) of restoring the U-turn, as that feature is web-only. 

Ah, I see. It’s a side-effect of the new handling of direct via-points – I can see where it’s going wrong but not yet why. I’ll try and work out why it’s doing that tomorrow!

I think this should be fixed now – have a play and let me know if not!

Richard

I fear I am seeing unchanged behaviour of the Test route . (Using website on Windows PC, Firefox, in case that is relevant. I had restarted the PC so I think will have picked up your latest version; not sure how the version can be detected .)

Happy New Year to you (and all), best wishes and thanks for more great cycling routing in 2026

And testing in Android found same unchanged result. (Using App v 2.0 (41); running Android 16 (36) on Samsung Galaxy A55.)

HTH

Have you tried redoing the route – i.e. setting the ‘allow/forbid uturn’ setting at the via points again? It won’t have remembered it from the previous save when the bug was present.