Symfony version(s) affected

7.1.9

Description

This is a recurring issue with Messenger: when failing, stamps like ErrorDetailsStamp are added and they get to big to be accepted by the transport. In the AMQP case, you get a "table too large for buffer" error, we also had this in the past with #34082

How to reproduce

1. dispatch a Messenger message through an AMQP (Rabbit) transport
2. make it fail with a big stack trace

Possible Solution

I'm currently unable to properly get more details on this issue, because the retry failure is hiding the full cause. In my use case, I'm getting a 400 from an API call, but I don't know how to intercept the stamps and reduce them as a workaround/troubleshooting for this.

Additional Context

No response