Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update global concurrency limits docs for removed create_if_missing behavior #15517

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/3.0/develop/global-concurrency-limits.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -118,9 +118,10 @@ The `concurrency`context manager allows control over the maximum number of concu
or asynchronous (`async`) version, depending on your use case. Here's how to use it:

<Tip>
**Concurrency limits are implicitly created in an inactive state**
**Concurrency limits are not implicitly created**

When using the `concurrency` context manager, if the provided `names` of the concurrency limits don't already exist, they are created in an inactive state.
When using the `concurrency` context manager, if the provided `names` of the concurrency limits don't already exist, then no limiting is enforced and a warning will be logged.
For stricter control, use `strict=True` to instead raise an error if no matching limits exist to block execution of the task.
</Tip>

**Sync**
Expand Down