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
However these messages are than stuck and might trigger false positives. This could be fixed with modifying the query like:
SELECT available_at FROM messenger_messages WHERE available_at < UTC_TIMESTAMP() AND queue_name NOT LIKE "%failed%" ORDER BY available_at ASC LIMIT 1
Another option would be to make the queues you want to monitor with QueueChecked configurable in the plugin config.
Ex: Enter a comma seperated list of queues to monitor (async, ...)
Please describe the feature you would like to see implemented.
It might happen that you have multiple queues configured on your installation. Ex: Routing of failed messages from async to async_failed. If so this async_failed queue is often ran manually as suggested in https://symfony.com/doc/current/messenger.html#saving-retrying-failed-messages
However these messages are than stuck and might trigger false positives. This could be fixed with modifying the query like:
SELECT available_at FROM messenger_messages WHERE available_at < UTC_TIMESTAMP() AND queue_name NOT LIKE "%failed%" ORDER BY available_at ASC LIMIT 1
Another option would be to make the queues you want to monitor with QueueChecked configurable in the plugin config.
Ex: Enter a comma seperated list of queues to monitor (async, ...)
Ideally a threshold can be set per queue, since their retry strategy & timeout might be different. https://symfony.com/doc/current/messenger.html#retries-failures
The text was updated successfully, but these errors were encountered: