Jump to solution
Details

The Fix

pip install celery==5.6.0

Based on closed celery/celery issue #9671 · 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
@@ -46,6 +46,13 @@ class Queues(dict): added automatically, but if this flag is disabled the occurrence of unknown queues in `wanted` will raise :exc:`KeyError`. + create_missing_queue_type (str): Type of queue to create for missing queues. + Must be either 'classic' (default) or 'quorum'. If set to 'quorum', + the broker will declare new queues using the quorum type.
fix.md
Option A — Upgrade to fixed release\npip install celery==5.6.0\nWhen NOT to use: Do not use this fix if you require backward compatibility with classic queues only.\n\n

Why This Fix Works in Production

  • Trigger: Adding task_create_missing_queues_type in order to autocreate missing queues with quorum type
  • Mechanism: The existing configuration does not allow setting the queue type for auto-created queues
  • Why the fix works: Adds two new optional settings that control how Celery auto-creates queues when task_create_missing_queues is enabled, addressing issue #9671. (first fixed release: 5.6.0).
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

  • Triggered by an upgrade/regression window: 4.0 breaks; 5.6.0 is the first fixed release.
  • The existing configuration does not allow setting the queue type for auto-created queues
  • Production symptom (often without a traceback): Adding task_create_missing_queues_type in order to autocreate missing queues with quorum type

Proof / Evidence

  • GitHub issue: #9671
  • Fix PR: https://github.com/celery/celery/pull/9815
  • First fixed release: 5.6.0
  • Affected versions: 4.0
  • 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.67

Discussion

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

“@Nusnus can you verify if this issue is legit?”
@auvipy · 2025-05-19 · source
“Hi @auvipy , I’ve worked on this and would be happy to open a PR if that’s okay”
@ghirailghiro · 2025-07-14 · source
“I guess this will also require some setting to change default exchange type, because quorum queues work with topic exchanges, not direct as classic ones…”
@M1ha-Shvn · 2025-07-15 · source
“> Hi @auvipy , I’ve worked on this and would be happy to open a PR if that’s okay”
@auvipy · 2025-07-15 · source

Failure Signature (Search String)

  • Adding task_create_missing_queues_type in order to autocreate missing queues with quorum type
  • - [x] I have included all related issues and possible duplicate issues
Copy-friendly signature
signature.txt
Failure Signature ----------------- Adding task_create_missing_queues_type in order to autocreate missing queues with quorum type - [x] I have included all related issues and possible duplicate issues

Error Message

Signature-only (no traceback captured)
error.txt
Error Message ------------- Adding task_create_missing_queues_type in order to autocreate missing queues with quorum type - [x] I have included all related issues and possible duplicate issues

What Broke

Auto-created queues default to classic type, causing potential compatibility issues with RabbitMQ quorum queues.

Why It Broke

The existing configuration does not allow setting the queue type for auto-created queues

Fix Options (Details)

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

pip install celery==5.6.0

When NOT to use: Do not use this fix if you require backward compatibility with classic queues only.

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/9815

First fixed release: 5.6.0

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

Get updates

We publish verified fixes weekly. No spam.

Subscribe

When NOT to Use This Fix

  • Do not use this fix if you require backward compatibility with classic queues only.

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

VersionStatus
4.0 Broken
5.6.0 Fixed

Related Issues

No related fixes found.

Sources

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