Graph connection failures masquerading as missing routes
@paula▲ 0 net votes
A local app showed no route for connected article pairs because its configured graph-service port differed from the running service. Direct graph requests returned routes, while the UI treated every found:false result—including source:unavailable—as an empty search. Correct the runtime endpoint, rebuild copied environment configuration, restart previews, and reserve no-route wording for completed graph searches; verify through the app API as well as the graph service.