Celery celery[sqs] no longer available? (Fix)

The Fix

pip install celery==5.4.0

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

Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.

Open PR/Commit

@@ -15,7 +15,7 @@ the ``celery[sqs]`` :ref:`bundle <bundles>`:
 .. code-block:: console
 
-    $ pip install celery[sqs]
+    $ pip install "celery[sqs]"

fix.md

Option A — Upgrade to fixed release\npip install celery==5.4.0\nWhen NOT to use: This fix is not applicable if the installation command is already correct.\n\n

Why This Fix Works in Production

Trigger: Users were unable to install the SQS version of Celery via pip, leading to confusion.
Mechanism: The documentation incorrectly stated the installation command for the SQS bundle
Why the fix works: Updated documentation to correct the installation command for the SQS bundle in Celery. (first fixed release: 5.4.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

The documentation incorrectly stated the installation command for the SQS bundle
Production symptom (often without a traceback): Users were unable to install the SQS version of Celery via pip, leading to confusion.

Proof / Evidence

GitHub issue: #8809
Fix PR: https://github.com/celery/celery/pull/8829
First fixed release: 5.4.0
Reproduced locally: No (not executed)
Last verified: 2026-02-09
Confidence: 0.95
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.80

Discussion

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

Jump to Sources Open on GitHub

“This is a doc bug. pip install 'celery[sqs]' works.”

@Nusnus · 2024-01-19 · source

“Fixed: https://docs.celeryq.dev/en/main/getting-started/backends-and-brokers/sqs.html#installation”

@Nusnus · 2024-01-31 · source

Failure Signature (Search String)

Users were unable to install the SQS version of Celery via pip, leading to confusion.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
Users were unable to install the SQS version of Celery via pip, leading to confusion.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
Users were unable to install the SQS version of Celery via pip, leading to confusion.

What Broke

Users were unable to install the SQS version of Celery via pip, leading to confusion.

Why It Broke

The documentation incorrectly stated the installation command for the SQS bundle

Fix Options (Details)

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

pip install celery==5.4.0

When NOT to use: This fix is not applicable if the installation command is already correct.

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

First fixed release: 5.4.0

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

When NOT to Use This Fix

This fix is not applicable if the installation command is already correct.

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.4.0	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.