Maximum parallel subworkflows

Feature Requests
1

Hello,

I think an option on the call workflow node would be great:

The idea is:

If you disable “wait for subworkflow completion”, I would like to have “maximum executions in parallel” to input the number of subworkflow that can be active at a time.

image
image662×942 47.5 KB

That would give the ability to fine-tune the load on the server, avoid hitting API rate, etc.

My use case:

I often want to process thousands of rows via complex subworkflows.

image
image2222×1028 139 KB

Right now I understand my ability would be either to process batches one by one, or launch all subworkflows.

I would like to be able to process multiple records at once but without launching all of them.
If I launch all of them my server crashed. And I can’t manage the queue generated by other workflows.

I hope I’m not missing something,
Thank you for your vote if you agree :slight_smile:

Cheers

2

Hi @Joachim_Brindeau

Don’t forget to vote yourself :wink:

I like using RabbitMQ to keep things clean and load under controll.
It is very easy to just push to a queue and have the other flow grab it from the queue. This can simplify workflows and also allows you to choose how many you want to run in parallel. :slight_smile:

Of course it would still be nice to have more options natively in n8n.
But this might help you in the meantime :slight_smile:

1 Like