Celery Documentation for worker_direct exchange is outdated

The Fix

pip install celery==5.3.0b2

Based on closed celery/celery issue #7972 · PR/commit linked

Production note: This usually shows up under retries/timeouts. Treat it as a side-effect risk until you can verify behavior with a canary + real traffic.

Open PR/Commit

@@ -2453,7 +2453,7 @@ This option enables so that every worker has a dedicated queue,
 
 The queue name for each worker is automatically generated based on
-the worker hostname and a ``.dq`` suffix, using the ``C.dq`` exchange.
+the worker hostname and a ``.dq`` suffix, using the ``C.dq2`` exchange.

fix.md

Option A — Upgrade to fixed release\npip install celery==5.3.0b2\nWhen NOT to use: This fix is not applicable if the documentation is already updated.\n\n

Why This Fix Works in Production

Trigger: Documentation for worker_direct exchange is outdated
Mechanism: Updated documentation to reflect the correct exchange to use with worker_direct.
Why the fix works: Updated documentation to reflect the correct exchange to use with worker_direct. (first fixed release: 5.3.0b2).

Production impact:

If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

Production symptom (often without a traceback): Documentation for worker_direct exchange is outdated

Proof / Evidence

GitHub issue: #7972
Fix PR: https://github.com/celery/celery/pull/7973
First fixed release: 5.3.0b2
Reproduced locally: No (not executed)
Last verified: 2026-02-09
Confidence: 0.85
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.61

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“Hey @alessio-b2c2 :wave:, Thank you for opening an issue”

@open-collective-bot · 2022-12-21 · source

“would you mind contributing this doc improvement?”

@auvipy · 2022-12-21 · source

“Done: https://github.com/celery/celery/pull/7973”

@alessio-b2c2 · 2022-12-21 · source

Failure Signature (Search String)

Documentation for worker_direct exchange is outdated
- [x] I have included all related issues and possible duplicate issues in this issue

Copy-friendly signature

signature.txt

Failure Signature
-----------------
Documentation for worker_direct exchange is outdated
- [x] I have included all related issues and possible duplicate issues in this issue

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
Documentation for worker_direct exchange is outdated
- [x] I have included all related issues and possible duplicate issues in this issue

What Broke

Users were misled by outdated documentation, causing incorrect task routing.

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install celery==5.3.0b2

When NOT to use: This fix is not applicable if the documentation is already updated.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

Fix reference: https://github.com/celery/celery/pull/7973

First fixed release: 5.3.0b2

Last verified: 2026-02-09. Validate in your environment.

When NOT to Use This Fix

This fix is not applicable if the documentation is already updated.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
Pin production dependencies and upgrade only with a reproducible test that hits the failing path.

Version Compatibility Table

Version	Status
5.3.0b2	Fixed

Related Issues

No related fixes found.

Cluster: celery:configuration-error Celery hub Celery best practices All hubs All clusters

Related clusters: Data consistency Duplicates Duplicate processing

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.

Celery Documentation for worker_direct exchange is outdated (Fix)