Symfony version(s) affected: 4.3.*

How to reproduce

• Try to handle a messenger message that fails... and allow it to fail until it goes to the failure transport
• Once on the failure transport, use messenger:failed:retry to retry the message. But, make sure it fails again.
• Try to view the specific information about the message - e.g. messenger:failed:show <id>. It will lose details about its exception. I think they are probably still there... but not being read correctly.

Message on failure transport before retrying:

Message on failure transport after retrying:

Possible Solution
We need to figure out if the exception information is being lost on redelivery (and if that's the case, make it not lost) or if it is present, but not being read correctly.