Searching for used subflows - help!

(Yeah, I'm a subflow person)
I have a few machines and am pathetic at keeping the subflows up to date on all machines.

I know I have been here before, but this wasn't resolved and I've been bitten agin by the same problem.

Problem I just found:
One of the machines has a better documented version of the subflow.
(No big deal)

I decided to move/copy it to the other machine.

Exported it.
Imported it.

No check existing and so I have two versions. :cry:
Not to be put off, I rename the OLD one and thought I would be able to search for the OLD version (on all tabs) and put the new version there.

Ain't happening.

When I search for the name, all I get/see is the subflow listing.

Sorry, but how can I do what I want to do?
Thanks in advance.

Well, I PAINFULLY went through and found all the OLD instances and replaced them with the new one.

All - now - good.

But the twist that really (now) also annoys me:

I didn't give the instances Names - they were just left empty.
Did a search and all the instances were shown.

:crying_cat:

Not worth worrying about any more, but it is annoying.

Hi @Trying_to_learn

For future reference, in the Info sidebar there's a Subflows section. Alongside each subflow is a number telling you how many instances of the subflow exist.

If you hover your mouse over it, you can click and it will open up the search dialog listing the instances.

1 Like

Thanks.

(Just saying)

To me that is not intuitive to get the search thing happening.

But I'll try to remember it for next time it happens to me.
(Your help is appreciated though.)

IMHO people should not use subflows at all, but rather use reusable singleton groups, called via link-calls.

  1. subflows are actually MACROs. So if you have a subflow containing 50 nodes, each instance creates a new node-set replica (i.e. 10 subflow instances create 500 nodes, growing exponentially and impacting performace, memory consumption & load/save time).
  2. subflows are tricky & confusing WRT memory contexts, especially when you nest subflows within subflows, and need to figure out your level in the hierarchy ($parent.$parent...)
  3. link-calls can be called using dynamic named targets, so you don't need to care where they are located and have to wire them