From 85431da510613ed84a18dba88eb815da0f6a4eae Mon Sep 17 00:00:00 2001 From: John Votta Date: Mon, 30 Mar 2026 16:53:44 -0700 Subject: [PATCH 1/3] Document behavior of Tasks without a fairness key Co-Authored-By: Claude Sonnet 4.6 --- docs/develop/task-queue-priority-fairness.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/develop/task-queue-priority-fairness.mdx b/docs/develop/task-queue-priority-fairness.mdx index 0152d59bd8..4d12f1214d 100644 --- a/docs/develop/task-queue-priority-fairness.mdx +++ b/docs/develop/task-queue-priority-fairness.mdx @@ -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 From bf6570599bca131b01831adca763e1e7aa2434c0 Mon Sep 17 00:00:00 2001 From: John Votta Date: Fri, 3 Apr 2026 15:49:26 -0700 Subject: [PATCH 2/3] Replace em-dash with semicolon in unkeyed Tasks sentence --- docs/develop/task-queue-priority-fairness.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/develop/task-queue-priority-fairness.mdx b/docs/develop/task-queue-priority-fairness.mdx index 4d12f1214d..ec870f2507 100644 --- a/docs/develop/task-queue-priority-fairness.mdx +++ b/docs/develop/task-queue-priority-fairness.mdx @@ -310,7 +310,7 @@ haven't dispatched yet. 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. +Unkeyed Tasks do not bypass Fairness; they compete as one group alongside all explicitly keyed Tasks. ### Using Fairness and Priority together From cbac8bdfe636e2301232db954a20c4db9877e48d Mon Sep 17 00:00:00 2001 From: Milecia McG <47196133+flippedcoder@users.noreply.github.com> Date: Thu, 9 Apr 2026 09:34:08 -0500 Subject: [PATCH 3/3] Apply suggestion from @flippedcoder --- docs/develop/task-queue-priority-fairness.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/develop/task-queue-priority-fairness.mdx b/docs/develop/task-queue-priority-fairness.mdx index d47503c017..bac9521cc6 100644 --- a/docs/develop/task-queue-priority-fairness.mdx +++ b/docs/develop/task-queue-priority-fairness.mdx @@ -309,6 +309,7 @@ haven't dispatched yet. 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.