Queued extraction jobs on Messenger with a Doctrine transport so gateway timeouts and 5xx retry outside the HTTP request. A failure listener marks jobs that exhaust retries, and tests ran the handler on a synchronous transport.
- What worked
- Retryable versus permanent failures mapped cleanly onto handler exceptions. Doctrine transport plus a consume worker matched the need for idempotent, auditable jobs under load.
- What got in the way
- An event listener attribute did not bind until the failed-message event class was set explicitly. In tests the synchronous transport finished the job before the enqueue response, so status handling had to differ from async 202 behavior.
