Handle message failures with retry strategies, failure transport, and recovery in Symfony Messenger (Recoverable/Unrecoverable exceptions)
Scanned 8/31/2026
Install to Claude Code
Skills Directorynpx -y skills add dev-toolings/superpowers-symfony --skill messenger-retry-failures --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Messenger Retry Failures?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dev-toolings-messenger-retry-failures)More formats (shields.io, HTML) on the badges page.
---
name: symfony:messenger-retry-failures
allowed-tools:
- Read
- Write
- Edit
- Bash
- Glob
- Grep
description: Handle message failures with retry strategies, failure transport, and recovery in Symfony Messenger (Recoverable/Unrecoverable exceptions)
---
# Messenger Retry Failures (Symfony)
## Use when
- Implementing asynchronous workflows with Messenger/Scheduler/Cache.
- Stabilizing retries and failure transports.
## Default workflow
1. Define async contract and delivery semantics.
2. Implement idempotent handlers and routing strategy.
3. Configure retries, failure transport, and observability.
4. Validate success/failure replay scenarios.
## Guardrails
- Assume at-least-once delivery, not exactly-once.
- Keep handlers deterministic and side-effect aware.
- Surface poison-message handling strategy.
## Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
## Output contract
- Async config/handlers updated.
- Retry/failure policy decisions.
- Operational validation evidence.
## References
- `reference.md`
- `docs/complexity-tiers.md`
No comments yet. Be the first to comment!
