diff --git a/docs/configuration/images/queue-failures.png b/docs/configuration/images/queue-failures.png new file mode 100644 index 00000000..636289fa Binary files /dev/null and b/docs/configuration/images/queue-failures.png differ diff --git a/docs/configuration/images/queue-retry-strategy.png b/docs/configuration/images/queue-retry-strategy.png new file mode 100644 index 00000000..6bdefd91 Binary files /dev/null and b/docs/configuration/images/queue-retry-strategy.png differ diff --git a/docs/configuration/settings.rst b/docs/configuration/settings.rst index 9aac76f0..62c4edbb 100644 --- a/docs/configuration/settings.rst +++ b/docs/configuration/settings.rst @@ -536,7 +536,14 @@ See `https://symfony.com/doc/5.4/messenger.html#amazon-sqs `_ Advanced setting ================ @@ -544,12 +551,26 @@ Advanced setting Retry strategy -------------- -TBD +When the processing of a message fails, the message is sent back to the queue for another try. You can adjust this behaviour in this section. +See `https://symfony.com/doc/5.4/messenger.html#retries-failures `_ for more details. + +The screenshot below shows the default values. + +.. image:: images/queue-retry-strategy.png + :width: 600 + :alt: Retry strategy defaults Queue for failures ------------------ -TBD +If a message fails all its retries, it's discarded by default. To avoid this happening, you can optionally configure a queue for failures. +For more details see the documentation on `https://symfony.com/doc/5.4/messenger.html#saving-retrying-failed-messages `_. + +The screenshot below shows the example of configuring the failure queue using the Doctrine transport. + +.. image:: images/queue-failures.png + :width: 600 + :alt: Example of failure configuration Notification settings *********************