Celery Ability to customize `Received task` message (Fix)

The Fix

pip install celery==5.1.0rc1

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

@@ -52,6 +52,11 @@
 logger = get_logger(__name__)
 
+#: Format string used to log task receipt.
+LOG_RECEIVED = """\
+Task %(name)s[%(id)s] received\

fix.md

Option A — Upgrade to fixed release\npip install celery==5.1.0rc1\nWhen NOT to use: This fix should not be used if static logging messages are required.\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 'Received task' logging message was fixed and not customizable
Why the fix works: Added LOG_RECEIVED to allow customization of the 'Received task' logging message. (first fixed release: 5.1.0rc1).

Production impact:

If left unfixed, retries/timeouts can trigger duplicate external side-effects (double charges, duplicate emails, repeated writes).

Why This Breaks in Prod

The 'Received task' logging message was fixed and not customizable
Production symptom (often without a traceback): - [X] I have included all related issues and possible duplicate issues in this issue

Proof / Evidence

GitHub issue: #6756
Fix PR: https://github.com/celery/celery/pull/6758
First fixed release: 5.1.0rc1
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.74

Discussion

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

Jump to Sources Open on GitHub

“Hey @daveisfera :wave:, Thank you for opening an issue”

@open-collective-bot · 2021-05-05 · source

Failure Signature (Search String)

- [X] I have included all related issues and possible duplicate issues in this issue
Should be a non-breaking change that only adds a customization point

Copy-friendly signature

signature.txt

Failure Signature
-----------------
- [X] I have included all related issues and possible duplicate issues in this issue
Should be a non-breaking change that only adds a customization point

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
Should be a non-breaking change that only adds a customization point

What Broke

Logging messages for received tasks were static and could not be customized.

Why It Broke

The 'Received task' logging message was fixed and not customizable

Fix Options (Details)

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

pip install celery==5.1.0rc1

When NOT to use: This fix should not be used if static logging messages are required.

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

First fixed release: 5.1.0rc1

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

When NOT to Use This Fix

This fix should not be used if static logging messages are required.

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.1.0rc1	Fixed

Related Issues

No related fixes found.

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

Related clusters: Configuration error Data consistency Duplicate processing

Sources

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