symfony:messenger-retry-failures

Configure Symfony Messenger retries, idempotent handlers, and failure transports.

187|17|Updated Dec 17, 2025

Search Tags:#async #symfony #idempotency #failures #retries #messenger

Ready to run

npx skills add https://github.com/MakFly/superpowers-symfony --skill symfony-messenger-retry-failures

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: symfony:messenger-retry-failures
Source: https://github.com/MakFly/superpowers-symfony/tree/main/skills/messenger-retry-failures
Command: npx skills add https://github.com/MakFly/superpowers-symfony --skill symfony-messenger-retry-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers build robust asynchronous messaging systems in Symfony by implementing strategies for handling message retries, failures, and ensuring operational visibility.

Core Features & Use Cases

Idempotent Handlers: Design message handlers that can be safely executed multiple times without unintended side effects.
Configurable Retry Strategies: Define custom logic for how and when messages should be retried, including exponential backoff.
Failure Transport Management: Configure a dedicated transport for failed messages and provide tools for their inspection and reprocessing.
Use Case: When a payment processing message fails due to a temporary gateway timeout, this Skill ensures it's retried with increasing delays until successful, or moved to a failed queue for manual intervention if it persists.

Quick Start

Use the symfony:messenger-retry-failures skill to configure exponential backoff and a failed transport for your async messenger messages.

Frequently Asked Questions about symfony:messenger-retry-failures

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I configure Symfony Messenger retries with exponential backoff for failed messages?▼

Configure Symfony Messenger retries with exponential backoff by defining custom retry logic that delays failed messages with increasing intervals. This Skill implements these configurable retry strategies to stabilize critical background tasks until successful or moved to a failed queue.

What is idempotency in asynchronous message handling and when do I need it?▼

Idempotency in asynchronous message handling ensures handlers execute safely multiple times without unintended side effects. You need idempotent handlers when implementing at-least-once delivery semantics, which guarantees deterministic processing even if messages are retried.

How do I set up a Symfony Messenger failure transport for poison-message handling?▼

Set up a Symfony Messenger failure transport by configuring a dedicated transport to isolate poison-messages. This Skill provides operational visibility and tools for inspecting and reprocessing these failed background tasks for manual intervention.

Does this approach to async workflow resilience work for temporary gateway timeouts?▼

Yes, this approach to async workflow resilience works for temporary gateway timeouts. It automatically retries the failed message with increasing delays until successful, satisfying at-least-once delivery requirements for critical background tasks.

What is the best way to monitor Symfony Messenger message processing failures?▼

The best way to monitor Symfony Messenger message processing failures is to configure operational visibility over a dedicated failure transport. This Skill provides the necessary tools for robust monitoring, inspection, and reprocessing of failed messages.