# Adding Junction node ids to search results?

**URL:** <https://discourse.nodered.org/t/adding-junction-node-ids-to-search-results/100900>\
**Category:** Core Development\
**Created:** [4 May 2026 08:38 UTC](https://discourse.nodered.org/t/adding-junction-node-ids-to-search-results/100900 "2026-05-04T08:38:19Z")\
**Posts on this page:** 4\
**Page:** 1

<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:** [4 May 2026 08:38 UTC](https://discourse.nodered.org/t/adding-junction-node-ids-to-search-results/100900/1 "2026-05-04T08:38:19Z")

</div>

Hi There,

I have a use case whereby it would be useful to have the junction nodes as part of a search result. It's very obscure so no surprise that junction nodes aren't part of the search results.

To illustrate my use case:

 ![Untitled](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/a/0a3236ad9da0b49450d76b65cbdabd5962d4d906.png)

Here I'm comparing two versions of my flow and the sidebar is showing a wire difference

 ![Screenshot 2026-05-04 at 10.30.11](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/f/cfec9a6827c7f768dc5dae654102847872008d6b.png)

Each wire is a node id so in this case node id `1fb88a2c8e3e0418` has been replaced by `d75c060fc66713cd` - turns out I replaced one junction node for another but that's not recognisable from the node id (which happens to be a junction node).

Because I didn't know it was a junction node, I did a search for the node id but I got zero results which is unusual since node ids are indexed by the search:

 ![Screenshot 2026-05-04 at 10.33.21](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/2/e2b73738beab27d7406069503d035d22451c571b.png)

So this is a bit confusing until I realised that it's a junction node:

 ![Screenshot 2026-05-04 at 10.34.44](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/d/5db9b44b5261f162cc193338584664f796245078.png)

I know it's a minor and obscure use-case but perhaps there is a reason for not including junctions in search results (probably because of the number of potential junctions) or whether it's actually something that has been missed and never asked for.

Cheers!

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [4 May 2026 08:59 UTC](https://discourse.nodered.org/t/adding-junction-node-ids-to-search-results/100900/2 "2026-05-04T08:59:56Z")

</div>

It was touched on a while back: [How to find a Junction - #3 by Steve-Mcl](https://discourse.nodered.org/t/how-to-find-a-junction/93461/3)

---

<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:** [4 May 2026 09:20 UTC](https://discourse.nodered.org/t/adding-junction-node-ids-to-search-results/100900/3 "2026-05-04T09:20:47Z")

</div>

Cheers, I've added a backlink to the [PR](https://github.com/node-red/node-red/issues/4967).

It's probably would also require extending the select/highlight functionality which doesn't IIRC support junction nodes, only groups and "real" nodes. I.e. even if the junction nodes were to be in the search results, there is no way to highlight them within the workspace.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [3 July 2026 09:21 UTC](https://discourse.nodered.org/t/adding-junction-node-ids-to-search-results/100900/4 "2026-07-03T09:21:37Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.