Improvement: Node Health Indicator Misleading in Certain Configurations

The node health feature, while generally useful, can sometimes mislead users into thinking everything is working well, even if there are configuration issues. For example, a user with mixed public and private channels experienced "no route" issues, yet the node health indicator showed 100% health. This gave a false sense of everything being fine.

I do not suggest changes at this point, but I'm raising this issue to track similar occurrences as they come up. Once we have more examples and a better understanding, we can consider improvements to the logic to avoid false negatives. There is no urgency, as the feature has been helpful for most users, but this is worth addressing for a small subset of rare cases. 😊


The issue names no files, tests, or entry points. Start by collecting further examples of 100% health with “no route” conditions, especially mixed public and private channels, and document the relevant configurations. Done means the occurrences are understood well enough to define a change that prevents misleading health results.

Written by the indexing model from the issue text.