You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/queue-concurrency.mdx
+2
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,8 @@ When you trigger a task, it isn't executed immediately. Instead, the task [run](
7
7
8
8
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.
9
9
10
+
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.
11
+
10
12
## Default concurrency
11
13
12
14
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
0 commit comments