Issue Feature Resolved

#110230Provide a Messenger failure transport with retry and failed:* commands

Stefan Bürk 07/19/26, 22:34 updated 11/04/26, 08:40

Description

Symfony Messenger ships a failure-transport + retry mechanism and the
messenger:failed:{show,retry,remove} commands, but TYPO3 does not expose them, so
a message a worker permanently rejects is lost.

TYPO3 should provide an opt-in failure transport, a per-transport retry strategy
and the console commands to inspect, retry and remove parked messages.

Expected

  • Opt-in via $GLOBALS['TYPO3_CONF_VARS']['SYS']['messenger']['failure_transport']
    (default empty = disabled). A ready-to-use “failed” transport reuses the
    sys_messenger_messages table with queue_name “failed”.
  • Per-transport retry strategy via
    ['SYS']['messenger']['transports'][<name>]['retry_strategy']
    (max_retries, delay, multiplier, max_delay). No entry = not retried.
  • Commands messenger:failed:show / :retry / :remove.
  • Async only: the handling reacts to the worker’s WorkerMessageFailedEvent and
    never affects a synchronous dispatch (SyncTransport).

Notes / open points (WIP)

  • retry command is reimplemented natively (re-handles a failed message on the bus
    with a ReceivedStamp for its original transport) rather than driving a Symfony
    worker; during retry no WorkerMessage* events are emitted, so a re-failure stays
    parked instead of flowing back through the retry/failure listeners.
  • Global (single) failure transport for now; per-transport override is a possible
    follow-up. messenger:stop-workers not wired yet.

Reviews 1

History 113

  1. Stefan Bürk commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-04T08:40:20+00:00" > 11/04/26, 08:40 </span>

    Applied in changeset commit:03f0ba95dc98005af7462a14d7f3c0d0015cde87.