https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36702
--- Comment #2 from David Cook <[email protected]> --- As noted on that RabbitMQ plugin link, having a task scheduler could solve the problem for both broker methods. Upon failure, a task could be enqueued to run X seconds later. That task could be to restart the background job. It could reset the job status and then for RabbitMQ mode it could send a new message. The number of background job tries could be tracked in the job. We need a task scheduler at some point anyway. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
