Celery Don’t list redis as stable backend and/or link to

The Fix

pip install celery==5.5.0

Based on closed celery/celery issue #8568 · 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

@@ -310,6 +310,7 @@ def __repr__(self):
         ),
         soft_shutdown_timeout=Option(0.0, type='float'),
+        enable_soft_shutdown_on_idle=Option(False, type='bool'),
         concurrency=Option(None, type='int'),
         consumer=Option('celery.worker.consumer:Consumer', type='string'),

fix.md

Option A — Upgrade to fixed release\npip install celery==5.5.0\nWhen NOT to use: This fix should not be used if the application relies on immediate task execution without considering shutdown behavior.\n\n

Why This Fix Works in Production

Trigger: - [x] I have included all related issues and possible duplicate issues in this issue
Mechanism: Redis was incorrectly listed as a stable backend despite significant caveats leading to potential data loss
Why the fix works: Adds a configuration option to enable soft shutdown on idle workers, which helps in requeuing ETA tasks during shutdown. (first fixed release: 5.5.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

Redis was incorrectly listed as a stable backend despite significant caveats leading to potential data loss
Production symptom (often without a traceback): - [x] I have included all related issues and possible duplicate issues in this issue

Proof / Evidence

GitHub issue: #8568
Fix PR: https://github.com/celery/celery/pull/9231
First fixed release: 5.5.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.71

Discussion

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

Jump to Sources Open on GitHub

“Closing for now, we may reopen if anyone disagrees that the issue should be closed.”

@Nusnus · 2024-09-25 · confirmation · source

“I agree with you. can you help to change the doc about redis? In recent times I found other back ends more stable then redis.…”

@auvipy · 2023-11-12 · source

“I can collaborate to reach that target as well. thanks for heads up Nusnus”

@auvipy · 2023-11-12 · source

“> I can collaborate to reach that target as well. thanks for heads up Nusnus 🚀🚀🚀”

@Nusnus · 2023-11-12 · source

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

signature.txt

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

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

Users experienced data loss when using ETA tasks with Redis due to abrupt shutdowns.

Why It Broke

Redis was incorrectly listed as a stable backend despite significant caveats leading to potential data loss

Fix Options (Details)

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

pip install celery==5.5.0

When NOT to use: This fix should not be used if the application relies on immediate task execution without considering shutdown behavior.

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

First fixed release: 5.5.0

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 immediate task execution without considering shutdown behavior.

Did This Fix Work in Your Case?

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

Prevention

Make timeouts explicit and test them (unit + integration) to avoid silent behavior changes.
Instrument retries (attempt count + reason) and alert on spikes to catch dependency slowdowns.

Version Compatibility Table

Version	Status
5.5.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.

Celery Don’t list redis as stable backend and/or link to issues/caveats (Fix)