Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sending queue blocked in case of any unsendable message #177

Closed
julianhofmann opened this issue May 23, 2023 · 1 comment · Fixed by #178
Closed

Sending queue blocked in case of any unsendable message #177

julianhofmann opened this issue May 23, 2023 · 1 comment · Fixed by #178
Labels
enhancement New feature or request

Comments

@julianhofmann
Copy link
Contributor

There are different reasons why a message from the queue cannot be sent:

The task hangs as soon as a message from the queue cannot be sent successfully. And on the next run, this error-causing entry is again taken from the queue and an attempt is made to send it - again with the same error.....

Solution
The queue should have the possibility to skip erroneous entries.

One idea would be to count up a counter and ignore such entries after X faulty attempts.
However, this should not happen silently, but the sender should also be informed. One possibility would be to expand the dispatch status accordingly (not yet sent/successful/erroneous) and to display it in different colors in the status bar (similar to what Solr indexing does).

@einpraegsam einpraegsam added the enhancement New feature or request label May 23, 2023
@julianhofmann
Copy link
Contributor Author

@einpraegsam, is there a chance to get this back-ported in v17 (TYPO3 v10)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants