The Fix
pip install celery==5.0.2
Based on closed celery/celery issue #6361 · 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.
@@ -46,7 +46,6 @@ class Queues(dict):
added automatically, but if this flag is disabled the occurrence
of unknown queues in `wanted` will raise :exc:`KeyError`.
- ha_policy (Sequence, str): Default HA policy for queues with none set.
max_priority (int): Default x-max-priority for queues with none set.
"""
Option A — Upgrade to fixed release\npip install celery==5.0.2\nWhen NOT to use: This fix should not be used if the application relies on HA policies for queue management.\n\n
Why This Fix Works in Production
- Trigger: - [x] I have included all related issues and possible duplicate issues in this issue
- Mechanism: The RabbitMQ setting task_queue_ha_policy is deprecated and has no effect on queue declaration
- Why the fix works: Removes the HA policy for RabbitMQ broker as it does not have any effect, addressing issue #6361. (first fixed release: 5.0.2).
- 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
- The RabbitMQ setting task_queue_ha_policy is deprecated and has no effect on queue declaration
- Production symptom (often without a traceback): - [x] I have included all related issues and possible duplicate issues in this issue
Proof / Evidence
- GitHub issue: #6361
- Fix PR: https://github.com/celery/celery/pull/6440
- First fixed release: 5.0.2
- Reproduced locally: No (not executed)
- Last verified: 2026-02-09
- Confidence: 0.75
- Did this fix it?: Yes (upstream fix exists)
- Own content ratio: 0.67
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“@auvipy @safwanrahman The fix that has been merged here does not address the problem”
Failure Signature (Search String)
- - [x] I have included all related issues and possible duplicate issues in this issue
- or possible duplicates to this issue as requested by the checklist above.
Copy-friendly signature
Failure Signature
-----------------
- [x] I have included all related issues and possible duplicate issues in this issue
or possible duplicates to this issue as requested by the checklist above.
Error Message
Signature-only (no traceback captured)
Error Message
-------------
- [x] I have included all related issues and possible duplicate issues in this issue
or possible duplicates to this issue as requested by the checklist above.
What Broke
Tasks may not be replicated as expected, leading to potential data loss in case of broker failure.
Why It Broke
The RabbitMQ setting task_queue_ha_policy is deprecated and has no effect on queue declaration
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install celery==5.0.2
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/6440
First fixed release: 5.0.2
Last verified: 2026-02-09. Validate in your environment.
When NOT to Use This Fix
- This fix should not be used if the application relies on HA policies for queue management.
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.0.2 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.