Skip to content

Commit 2da9e12

Browse files
Apply suggestions from code review
Co-authored-by: Olga Silva <[email protected]>
1 parent 46361d6 commit 2da9e12

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/content/docs/workflows/reference/limits.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,15 +42,15 @@ Many limits are inherited from those applied to Workers scripts and as documente
4242

4343
[^6]: Workflows will return a HTTP 429 rate limited error if you exceed the rate of new Workflow instance creation.
4444

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.
4646

4747
<Render file="limits_increase" product="workers" />
4848

4949
### `waiting` instances do not count towards instance concurrency limits
5050

5151
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.
5252

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:
5454

5555
```ts title="src/index.ts"
5656
import { WorkflowEntrypoint, WorkflowStep, WorkflowEvent } from 'cloudflare:workers';
@@ -99,7 +99,7 @@ export class MyWorkflow extends WorkflowEntrypoint<Env, Params> {
9999
}
100100
```
101101

102-
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.
103103

104104
### Increasing Workflow CPU limits
105105

0 commit comments

Comments
 (0)