Non-sidewalk pathway elements might be interfering with routing

[TCAT-UW]

Seems like a particular indoor skyway in Bellevue is interfering with the router's ability to find a route.
It may be that where the destination was set, was identified closest to the skyway, and the router was excluding the skyway from its available paths? That's a total conjecture, but the manner in which skyways and similar footpath elements that are not sidewalks are incorporated into the routing graph should be evaluated.

-The first scenario was routing to a point south of the skyway, which gave a successful route.
-The second scenario was advancing the destination to a point adjacent to the intersection between the sidewalk and the skyway, but still closer to the sidewalk. This did not yield a successful route. This is where I believe the bug or feature is.
-The third scenario was advancing the destination to a point north of the skyway on the sidewalk and this did give a successful route.
-The fourth image just shows what the bottom panel brings up (i.e., just another footpath with 0.9% incline) when the user inspects the skyway.