# Unconnected junction nodes

**URL:** <https://discourse.nodered.org/t/unconnected-junction-nodes/101383>\
**Category:** Feature Requests\
**Created:** [30 June 2026 21:09 UTC](https://discourse.nodered.org/t/unconnected-junction-nodes/101383 "2026-06-30T21:09:07Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [1 July 2026 09:50 UTC](https://discourse.nodered.org/t/unconnected-junction-nodes/101383/10 "2026-07-01T09:50:30Z")

</div>

> [@jf64](#):
>
> - But the bigger point: this still only tells me _which_ junction IDs are affected — it doesn't help me _locate_ them on the canvas,

That is indeed a problem. I've also played around with [orphan nodes](https://discourse.nodered.org/t/search-for-orphan-nodes/77783) (as I called them) but in my implementation, I ignored junctions for exactly that reason - there was no way to highlight them.

There is also no jQuery triggery to hack around that because junction nodes do not have an identifying id within the workspace, i.e. `$('#<node-id>')` will give you access to any node but not junction.

---

_[View the full topic](https://discourse.nodered.org/t/unconnected-junction-nodes/101383)._