#110230Provide a Messenger failure transport with retry and failed:* commands
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
-
Gerrit Code Review pushed patch set 2 for main to change 94837 status
NewUnder Review <span data-processor="relativetime" data-value="2026-07-19T22:38:14+00:00" > 07/19/26, 22:38 </span> -
Gerrit Code Review pushed patch set 3 for main to change 94837 <span data-processor="relativetime" data-value="2026-07-19T22:48:35+00:00" > 07/19/26, 22:48 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 94837 <span data-processor="relativetime" data-value="2026-07-19T23:12:55+00:00" > 07/19/26, 23:12 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 94837 <span data-processor="relativetime" data-value="2026-07-19T23:27:02+00:00" > 07/19/26, 23:27 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 94837 <span data-processor="relativetime" data-value="2026-07-19T23:39:31+00:00" > 07/19/26, 23:39 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 94837 <span data-processor="relativetime" data-value="2026-07-20T00:09:46+00:00" > 07/20/26, 00:09 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 94837 <span data-processor="relativetime" data-value="2026-07-20T00:25:25+00:00" > 07/20/26, 00:25 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 94837 <span data-processor="relativetime" data-value="2026-07-20T13:14:13+00:00" > 07/20/26, 13:14 </span>
-
Gerrit Code Review pushed patch set 10 for main to change 94837 <span data-processor="relativetime" data-value="2026-07-28T06:29:57+00:00" > 07/28/26, 06:29 </span>
-
Gerrit Code Review pushed patch set 11 for main to change 94837 <span data-processor="relativetime" data-value="2026-08-01T20:36:49+00:00" > 08/01/26, 20:36 </span>
-
Gerrit Code Review pushed patch set 12 for main to change 94837 <span data-processor="relativetime" data-value="2026-10-31T20:09:37+00:00" > 10/31/26, 20:09 </span>
-
Gerrit Code Review pushed patch set 13 for main to change 94837 <span data-processor="relativetime" data-value="2026-10-31T23:18:36+00:00" > 10/31/26, 23:18 </span>
-
Stefan Bürk commented and changed status
Under ReviewResolved done0 %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.