Symfony version(s) affected

5.4

Description

SQS has a limit of 262,144 bytes (256 KB) message size.

When there is an error during message handling, the ErrorDetailsStamp adds a stacktrace that can lead to a message bigger than this limit.

How to reproduce

• Dispatch messages with SQS with a redelivery policy that makes it retry a few times
• Throw an exception with a super big stack trace
• See it fails

Possible Solution

Not sure, maybe an option to remove stack trace from ErrorDetailsStamp

Additional Context

No response