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: src/content/docs/workflows/reference/limits.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,15 +42,15 @@ Many limits are inherited from those applied to Workers scripts and as documente
42
42
43
43
[^6]: Workflows will return a HTTP 429 rate limited error if you exceed the rate of new Workflow instance creation.
44
44
45
-
[^7]: Only instances with a `running` state count towards the concurrency limits. If an instance is in a`waiting` state it does not count these limits.
45
+
[^7]: Only instances with a `running` state count towards the concurrency limits. Instances in the`waiting` state are excluded from these limits.
46
46
47
47
<Renderfile="limits_increase"product="workers" />
48
48
49
49
### `waiting` instances do not count towards instance concurrency limits
50
50
51
51
Instances that are on a `waiting` state - either sleeping, waiting for a retry or waiting for an event - do **not** count towards concurrency limits. It means that other `queued` instances will be scheduled when an instance goes from a `running` state to a `waiting` one, usually the oldest instance queued, in a best-effort basis. This state transition - `running` to `waiting` - might not happen if the duration of the wait is too short.
52
52
53
-
As an example, let's say we have a workflow that does some work, waits 30 days, and continues other work:
53
+
For example, consider a Workflow that does some work, waits for 30 days, and then continues with more work:
While a given Workflow instance is waiting for 30 days to pass, it will go to a`waiting` state, allowing other `queued` instances to run - if concurrency limits are exhausted.
102
+
While a given Workflow instance is waiting for 30 days, it will transition to the`waiting` state, allowing other `queued` instances to run if concurrency limits are reached.
0 commit comments