You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ The default Magento's consumer behavior is to reject the message when an excepti
64
64
If you use a standard configuration for the queue (without a dead-letter exchange), the message will be discarded and not processed again.
65
65
66
66
This behavior will change a bit with this module. It will introduce an extra step that will check if the message has reached your retry limit,
67
-
if so, it will be discarded from RabbitMQ and sent to the `run_as_root_message` Mysql table and stay there until manual management through the admin panel.
67
+
if so, it will be discarded from RabbitMQ and sent to the `run_as_root_queue_error_message` Mysql table and stay there until manual management through the admin panel.
68
68
69
69
If the message has not reached the retry limit, it will be rejected, and RabbitMQ will send it to the dead letter exchange. The message will be routed automatically to the "delay" queue and stay there until de TTL time is reached.
70
70
After the TTL time is reached, the message will be returned to its original queue.
0 commit comments