Mar 24, 2025 · Mar 24, 2025
diff --git a/messenger.rst b/messenger.rst
    # remove all messages in the failure transport
    $ php bin/console messenger:failed:remove --all

    # remove only MyClass messages
    $ php bin/console messenger:failed:remove --class-filter='MyClass'

 If the message fails again, it will be re-sent back to the failure transport
 due to the normal :ref:`retry rules <messenger-retries-failures>`. Once the max
 retry has been hit, the message will be discarded permanently.
    The option to skip a message in the ``messenger:failed:retry`` command was
    introduced in Symfony 7.2

 .. versionadded:: 7.3

    The option to filter by a message class in the ``messenger:failed:remove`` command was
    introduced in Symfony 7.3

 Multiple Failed Transports
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
Original file line number	Diff line number	Diff line change
Expand Up		@@ -1312,6 +1312,9 @@ to retry them:
		# remove all messages in the failure transport
		$ php bin/console messenger:failed:remove --all

		# remove only MyClass messages
		$ php bin/console messenger:failed:remove --class-filter='MyClass'

OskarStark marked this conversation as resolved. Show resolvedHide resolved
		If the message fails again, it will be re-sent back to the failure transport
		due to the normal :ref:`retry rules <messenger-retries-failures>`. Once the max
		retry has been hit, the message will be discarded permanently.
Expand All		@@ -1321,6 +1324,11 @@ retry has been hit, the message will be discarded permanently.
		The option to skip a message in the ``messenger:failed:retry`` command was
		introduced in Symfony 7.2

		.. versionadded:: 7.3

		The option to filter by a message class in the ``messenger:failed:remove`` command was
		introduced in Symfony 7.3

		Multiple Failed Transports
		~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down