The Fix
pip install celery==5.3.5
Based on closed celery/celery issue #8615 · 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.
@@ -362,7 +362,7 @@ Provides arguments:
* ``request``
- This is a :class:`~celery.worker.request.Request` instance, and not
+ This is a :class:`~celery.app.task.Context` instance, and not
``task.request``. When using the prefork pool this signal
Option A — Upgrade to fixed release\npip install celery==5.3.5\nWhen NOT to use: This fix should not be applied if the documentation is already accurate.\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 documentation incorrectly stated the type of the `request` parameter as `Request` instead of `Context`
- Why the fix works: The documentation for the `task_revoked` signal handler was corrected to indicate that the `request` parameter is a `Context` instance instead of a `Request` instance. (first fixed release: 5.3.5).
- 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 type of the `request` parameter as `Request` instead of `Context`
- Production symptom (often without a traceback): - [x] I have included all related issues and possible duplicate issues in this issue
Proof / Evidence
- GitHub issue: #8615
- Fix PR: https://github.com/celery/celery/pull/8616
- First fixed release: 5.3.5
- 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.75
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“# Checklist - [x] I have checked the issues list for similar or identical bug reports. - [x] I have checked the pull requests list for existing proposed fixes. - [x] I have checked the commit log to find out if the bug was already fixed in”
Failure Signature (Search String)
- - [x] I have included all related issues and possible duplicate issues in this issue
- The documentation should be changed to say it is a `Context` instance.
Copy-friendly signature
Failure Signature
-----------------
- [x] I have included all related issues and possible duplicate issues in this issue
The documentation should be changed to say it is a `Context` instance.
Error Message
Signature-only (no traceback captured)
Error Message
-------------
- [x] I have included all related issues and possible duplicate issues in this issue
The documentation should be changed to say it is a `Context` instance.
What Broke
Users were misled about the type of the `request` parameter, causing confusion in implementation.
Why It Broke
The documentation incorrectly stated the type of the `request` parameter as `Request` instead of `Context`
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install celery==5.3.5
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/8616
First fixed release: 5.3.5
Last verified: 2026-02-09. Validate in your environment.
When NOT to Use This Fix
- This fix should not be applied if the documentation is already accurate.
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.3.5 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.