Replies: 2 comments 3 replies
-
The listener already implements the three available functions from laravel but I wouldn't be surprised if there were other options hidden away somewhere. What extra customisation did you have in mind? |
Beta Was this translation helpful? Give feedback.
0 replies
-
The main use case for us would be to implement a backoff strategy to prevent network issues. See https://laravel.com/docs/12.x/queues#dealing-with-failed-jobs /**
* Calculate the number of seconds to wait before retrying the job.
*
* @return array<int, int>
*/
public function backoff(): array
{
return [1, 5, 10];
} I also want to adjust the retries only for this job. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm using the auditing queue functionality.
In my system I sometimes have an issue that the job fails. Due to network issues for example.
I would love to adjust the implementation of
\OwenIt\Auditing\Listeners\ProcessDispatchAudit
so that I can add custom logic or the retry functionality that is available from Laravel.My suggestion would be to add a
config('audit.queue.listener')
which defaults to\OwenIt\Auditing\Listeners\ProcessDispatchAudit
but gives you the option to use other classes aswell.Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions