Skip to content

Cloud concurrency#

Only for n8n Cloud

This document discusses concurrency in n8n Cloud. Read self-hosted n8n concurrency control to learn how concurrency works with self-hosted n8n instances.

Too many concurrent executions can cause performance degradation and unresponsiveness. To prevent this and improve instance stability, n8n sets concurrency limits for production executions in regular mode.

Any executions beyond the limits queue for later processing. These executions remain in the queue until concurrency capacity frees up, and are then processed in FIFO order.

Concurrency limits#

n8n limits the number of concurrent executions for Cloud instances according to their plan:

  • Starter and Trial: 5
  • Pro (10k workflow executions, 15 active workflows): 20
  • Pro (50k workflow executions, 50 active workflows): 50
  • Enterprise (in regular mode): 200

Details#

Some other details about concurrency to keep in mind:

  • Concurrency control applies only to production executions: those started from a webhook or trigger node. It doesn't apply to any other kinds, such as manual executions, sub-workflow executions, or error executions.
  • You can't retry queued executions. Cancelling or deleting a queued execution also removes it from the queue.
  • On instance startup, n8n resumes queued executions up to the concurrency limit and re-enqueues the rest.

Comparison to queue mode#

Feature availability

Queue mode is available for Cloud Enterprise plans. To enable it, contact n8n.

Concurrency in queue mode is a separate mechanism from concurrency in regular mode. In queue mode, the concurrency settings determine how many jobs each worker can run in parallel. In regular mode, concurrency limits apply to the entire instance.