At a glance
- How the limit worksn8n Cloud limits how many production executions run at the same time, based on your plan.
- What counts toward itOnly production executions count: those started by a webhook or trigger node.
- Working with the queueA queued execution can't be retried.
How the limit works
- n8n Cloud limits how many production executions run at the same time, based on your plan.
- Executions over the limit wait in a queue until capacity frees up, then run in FIFO order. They are not dropped.
- The executions tab of a project or workflow shows the number of active executions and your plan's limit at the top.
What counts toward it
- Only production executions count: those started by a webhook or trigger node.
- Manual executions, sub-workflow executions and error executions do not count.
- Test evaluations use a separate per-plan limit.
Working with the queue
- A queued execution can't be retried. Cancelling or deleting it removes it from the queue.
- When the instance starts up, n8n resumes queued executions up to the limit and re-queues the rest.
- Queue mode, where workers each have their own concurrency setting, is available on n8n Cloud Enterprise plans by contacting n8n.
Updated 2026-11-02. General guidance, not advice for your situation; we scope each project in writing before any work starts.
Questions people ask first
Will a queued execution be lost?
No. It stays in the queue until capacity frees up, unless you cancel or delete it.
Does testing in the editor use up the limit?
No. Manual executions are not counted.
Tell us what you need built.
Tell us the process and the tools involved, or call. We reply with questions or a written scope.
hello@pushbuild.com