Dan, I can open that route with no issue.

I'd suggest checking if it's the same on the website.

Saving under a different name.

Closing the app and restarting the phone. 

And variations of the above

Hobbes, the route you have open there isn't the same as my route (mine ends in Portmeirion, yours ends in Anglesey).

The website displays the route fine, it's just a problem on the app.

The problem persists across app restarts 

Saving the route as a new name *did* make the problem go away, interestingly: https://cycle.travel/map/journey/955835

Hobbes, the route you have open there isn't the same as my route (mine ends in Portmeirion, yours ends in Anglesey).

Dan, it's the route you included in your post. 

Glad the issue is solved. 

It isn't. Open the URL in a web browser and you'll see it ends in Portmeirion.

I'd say the issue has been worked around rather than fixed, the original route is still rendering incorrectly!

Dan, it is the route you included in your post. 

What is interesting, though, is that having  opened the route on the website, saved it, then opened it in the app, the end points are different as you have pointed out. 

That is certainly odd behaviour. 

I wonder if you planned it on the website or the app? Is it an imported route?

That’s odd! There’s something screwy around mile 150 (Birmingham area) on the website too. I wonder if there’s some weirdness with the map data there. I’m not anywhere near a computer right now so can’t really dig into it but will take a look when I can. 

Thanks Richard!

I noticed that if I just move one node a tiny bit the route fixes itself too, so it's not a massive deal. Seems like maybe a one time data corruption whenever this particular version of the route was saved.

Cosmic rays? :p