From 28c7a8eaa24984ad5649305c7d1e8db9ab4bf2c4 Mon Sep 17 00:00:00 2001 From: James Ritchie Date: Wed, 5 Mar 2025 17:51:43 +0000 Subject: [PATCH] Clarifies only executing runs count towards concurrency --- docs/queue-concurrency.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/queue-concurrency.mdx b/docs/queue-concurrency.mdx index 3529eaa44c..b76e374695 100644 --- a/docs/queue-concurrency.mdx +++ b/docs/queue-concurrency.mdx @@ -7,6 +7,8 @@ When you trigger a task, it isn't executed immediately. Instead, the task [run]( Controlling concurrency is useful when you have a task that can't be run concurrently, or when you want to limit the number of runs to avoid overloading a resource. +It's important to note that only actively executing runs count towards concurrency limits. Runs that are delayed or waiting in a queue do not consume concurrency slots until they begin execution. + ## Default concurrency By default, all tasks have an unbounded concurrency limit, limited only by the overall concurrency limits of your environment. This means that each task could possibly "fill up" the entire