Celery Stamping documentation is not completely accurate

The Fix

pip install celery==5.5.3

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

@@ -1259,19 +1259,25 @@ the external monitoring system, etc.
             return {'monitoring_id': uuid4().hex}
 
-.. note::
+.. important::

fix.md

Option A — Upgrade to fixed release\npip install celery==5.5.3\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 regarding the `stamped_headers` key was outdated and unclear
Why the fix works: Enhanced the documentation to clarify that the `stamped_headers` key is optional in visitor methods. (first fixed release: 5.5.3).

Why This Breaks in Prod

The documentation regarding the `stamped_headers` key was outdated and unclear
Production symptom (often without a traceback): - [x] I have included all related issues and possible duplicate issues in this issue

Proof / Evidence

GitHub issue: #9694
Fix PR: https://github.com/celery/celery/pull/9697
First fixed release: 5.5.3
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.76

Discussion

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

Jump to Sources Open on GitHub

“I’ve enhanced the docs to clarify that you do not have to include the stamped_headers key (_in any method_), as the issue also suggests”

@Nusnus · 2025-05-08 · 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 may have been confused about the necessity of including the `stamped_headers` key.

Why It Broke

The documentation regarding the `stamped_headers` key was outdated and unclear

Fix Options (Details)

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

pip install celery==5.5.3

When NOT to use: This fix should not be applied if the documentation is already accurate.

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

First fixed release: 5.5.3

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.5.3	Fixed

Related Issues

No related fixes found.

Cluster: celery:webhook Celery hub Celery best practices All hubs All clusters

Related clusters: Configuration error Data consistency Duplicates

Sources

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

Celery Stamping documentation is not completely accurate (Fix)