Great question. At the moment n8n doesn’t have a built-in setting to limit concurrency for just one specific workflow. Concurrency limits apply to the whole instance, so you can’t natively make one workflow strictly single-threaded while letting others run in parallel.
The usual approach for this scenario is to add a queue in front of the workflow that must run sequentially. Instead of processing immediately on trigger, you push each request into a queue and have a separate worker workflow consume that queue one item at a time. This guarantees that Workflow 1 runs strictly sequentially, while Workflow 2 can continue to execute concurrently as normal.
I understand the limitation now. I will proceed with the suggested approach and split the process into two workflows: one to handle the queueing and a separate worker workflow to process the items sequentially.
I’m really happy to hear this helped
If this solution solved the issue for you, please consider leaving a like or marking the reply as the solution ( it helps others find the answer more easily and also supports community contributors.)
