Stop / Abort / Kill a SubFlow


I'm probably missing something obvious but... Is there a way to force a SubFlow that is processing an asynchronous task that might take a minute or two to complete to immediately stop?

I feel it might be complicated or 'bad' to have (for example) multiple polling points within each SubFlow checking a global variable.

Thoughts welcomed!



Ok, my take:

Subflows are limited to one input.

But what happens inside is another story.

Just inside the subflow, test if the message has a specific topic.
If it doesn't go to the existing nodes.

If it does have that topic, then signal the other nodes in the subflow to stop.

That is kind of what I mean.

Understand what I mean?

1 Like

Hi Trying_to_learn,

That was pretty much the only way I could see to terminate SubFlows as well. Poll / check a variable periodically while inside the SubFlow (Switch node) and, if the conditions are met, jump somewhere else. The negative of this is the need to periodically check...

Any other process or method would be appreciated!


That isn't what @Trying_to_learn was suggesting. Send in a message with a specific topic and in the subflow use that message to stop your process. No polling or variables required.

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