I have this written as a bug here:
Did you have the issue with the in-sim planner, too?
If so, I can edit the title of my bug to include both.
However, Matt at WT told me that they aren’t responsible for the route finding code for the in-sim EFB (which I find crazy — we have two different route finding codes in the sim that produce two different results…) and are only responsible for it in the web-based planner.
However, if this bug happens in both places it would, maybe, point to a nav data issue rather than a route finding issue, specifically.
This is how I felt. It was exhausting and pointless. The more you try to settle into doing what you just did in 2020, the more you find issues getting in the way of that in 2024.