The Fix
pip install celery==5.5.0
Based on closed celery/celery issue #9383 · 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.
@@ -505,13 +505,14 @@ def _error_handler(exc, interval, next_step=CONNECTION_RETRY_STEP):
retry_disabled = not self.app.conf.broker_connection_retry
- warnings.warn(
- CPendingDeprecationWarning(
- f"The broker_connection_retry configuration setting will no longer determine\n"
repro.py
"""myapp.py
Usage::
(window1)$ python myapp.py worker -l INFO
(window2)$ python
>> from myapp import add
>> add.delay(16, 16).get()
32
You can also specify the app to use with the `celery` command,
using the `-A` / `--app` option::
$ celery -A myapp worker -l INFO
With the `-A myproj` argument the program will search for an app
instance in the module ``myproj``. You can also specify an explicit
name using the fully qualified form::
$ celery -A myapp:app worker -l INFO
"""
from time import sleep
from celery import Celery
app = Celery(
'myapp',
broker='amqp://guest@localhost//',
# ## add result backend here if needed.
# backend='rpc'
task_acks_late=True
)
@app.task
def add(x, y):
sleep(10)
return x + y
if __name__ == '__main__':
app.start()
verify
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.
fix.md
Option A — Upgrade to fixed release\npip install celery==5.5.0\nWhen NOT to use: This fix should not be applied if the warning behavior is intentionally suppressed.\n\n
Why This Fix Works in Production
- Trigger: Missing CPendingDeprecationWarning from Celery v5.4.0
- Mechanism: Modifies the warning behavior for the broker_connection_retry setting in Celery 6.0, ensuring it only triggers when necessary.
- Why the fix works: Modifies the warning behavior for the broker_connection_retry setting in Celery 6.0, ensuring it only triggers when necessary. (first fixed release: 5.5.0).
Production impact:
- If left unfixed, retries/timeouts can trigger duplicate external side-effects (double charges, duplicate emails, repeated writes).
Why This Breaks in Prod
- Production symptom (often without a traceback): Missing CPendingDeprecationWarning from Celery v5.4.0
Proof / Evidence
- GitHub issue: #9383
- Fix PR: https://github.com/celery/celery/pull/9227
- First fixed release: 5.5.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.43
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“Wait it is expected, no? - https://github.com/celery/celery/issues/9225 - https://github.com/celery/celery/pull/9227”
“> Wait it is expected, no? > > * Confusing warning about broker_connection_retry_on_startup #9225 > * Show broker_connection_retry_on_startup warning only if it evaluates as False…”
Failure Signature (Search String)
- Missing CPendingDeprecationWarning from Celery v5.4.0
- - [x] I have included all related issues and possible duplicate issues
Copy-friendly signature
signature.txt
Failure Signature
-----------------
Missing CPendingDeprecationWarning from Celery v5.4.0
- [x] I have included all related issues and possible duplicate issues
Error Message
Signature-only (no traceback captured)
error.txt
Error Message
-------------
Missing CPendingDeprecationWarning from Celery v5.4.0
- [x] I have included all related issues and possible duplicate issues
Minimal Reproduction
repro.py
"""myapp.py
Usage::
(window1)$ python myapp.py worker -l INFO
(window2)$ python
>> from myapp import add
>> add.delay(16, 16).get()
32
You can also specify the app to use with the `celery` command,
using the `-A` / `--app` option::
$ celery -A myapp worker -l INFO
With the `-A myproj` argument the program will search for an app
instance in the module ``myproj``. You can also specify an explicit
name using the fully qualified form::
$ celery -A myapp:app worker -l INFO
"""
from time import sleep
from celery import Celery
app = Celery(
'myapp',
broker='amqp://guest@localhost//',
# ## add result backend here if needed.
# backend='rpc'
task_acks_late=True
)
@app.task
def add(x, y):
sleep(10)
return x + y
if __name__ == '__main__':
app.start()
What Broke
Users did not receive expected deprecation warnings, leading to confusion about configuration changes.
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 applied if the warning behavior is intentionally suppressed.
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/9227
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 applied if the warning behavior is intentionally suppressed.
Verify Fix
verify
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.
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.5.0 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.