From 96ced64d85f8bf08429537e841c0829cb34d4179 Mon Sep 17 00:00:00 2001 From: Deborah Barnard Date: Tue, 11 Jun 2024 09:56:38 +0100 Subject: [PATCH] rephrase --- docs/hosting/scaling/concurrency-control.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hosting/scaling/concurrency-control.md b/docs/hosting/scaling/concurrency-control.md index d893a9fdd..9e993f990 100644 --- a/docs/hosting/scaling/concurrency-control.md +++ b/docs/hosting/scaling/concurrency-control.md @@ -6,7 +6,7 @@ contentType: explanation In regular mode, n8n doesn't limit how many production executions may run at the same time. This can lead to a scenario where too many concurrent executions thrash the event loop, causing performance degradation and unresponsiveness. -To prevent this, you can set a concurrency limit for production executions in regular mode. This allows for more than one production execution to run concurrently, and queues up any concurrent production executions over the limit. These executions remain in the queue until concurrency capacity frees up, and are then processed in FIFO order. +To prevent this, you can set a concurrency limit for production executions in regular mode. Use this to control how many production executions run concurrently, and queue up any concurrent production executions over the limit. These executions remain in the queue until concurrency capacity frees up, and are then processed in FIFO order. Concurrency control is disabled by default. To enable it: