Hi, I have this workflow with many subworkflows. If I am on the cloud plan, will it register as one 1 execution for the main and sub-workflows, or one for the main workflow plus one for each sub-workflow? Also, will this count as more than one concurrent execution?
I think that this will count as 7 total executions, and 2 concurrent executions. One for the main, and one for the sub-workflow step that it is on. Did I understand correctly?
@comfdy so this whole “concurrent execution” thing is basically just the cloud provider telling us, "How many jobs can run at the exact same time?
Think of it like this: on our plan, the rule is five concurrent runs max. That’s our hard limit. We can only have five workflows actually active and doing stuff at once.
The key takeaway is that you can mix and match, it could be five different types of workflows, or five instances of the exact same workflow, it doesn’t matter. The total count of running jobs can’t go over five. It’s like a five lane highway; once all five lanes are full, the sixth car has to wait
When you run a workflow that calls sub-workflows using the standard sub-workflow mechanism (e.g., the Execute Workflow or Execute Sub-workflow node), n8n Cloud only counts the main (parent) workflow execution towards your plan’s execution limits.
Concurrency limits on n8n Cloud apply only to production executions started from a trigger (like a webhook or schedule) in the main workflow. Sub-workflow executions do not count towards your concurrency limit. Only the main workflow execution is counted for concurrency.
“7 total executions and 2 concurrent executions” is not correct—it will be 1 execution and 1 concurrent execution for the main workflow, regardless of how many sub-workflows are called.