Skip to content

Document behavior of Tasks without a fairness key #4367

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.

Sign up for GitHub

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

Open
jpvotta wants to merge 3 commits into
base: main
Choose a base branch
from
+5 −0
Open

Document behavior of Tasks without a fairness key #4367

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
85431da
Document behavior of Tasks without a fairness key
jpvotta Mar 30, 2026
bf65705
Replace em-dash with semicolon in unkeyed Tasks sentence
jpvotta Apr 3, 2026
3d8fb45
Merge branch 'main' into docs/fairness-unkeyed-task-behavior
jpvotta Apr 3, 2026
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: 5 additions & 0 deletions docs/develop/task-queue-priority-fairness.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -307,6 +307,11 @@ haven't dispatched yet.
alt="High-level of how fairness works"
/>

Tasks that do not have a `fairness_key` set are grouped together under an implicit empty-string key.
All unkeyed Tasks share this single default bucket and participate in the same round-robin dispatch alongside named fairness keys, with a default weight of 1.0.
This means Fairness adoption can be incremental: you can assign fairness keys to some tenants but not others.
Unkeyed Tasks do not bypass Fairness; they compete as one group alongside all explicitly keyed Tasks.

### Using Fairness and Priority together

When you use Fairness and Priority together, Priority determines which sub-queue Tasks go into. A single Task Queue with
Expand Down
Loading