Skip to content

MaxAttemptsExceededException triggered due to overlapping job #43502

Answered by garrettboone
garrettboone asked this question in Q&A
Discussion options

You must be logged in to vote

It seems that without the ->releaseAfter(<seconds>) an overlapping job will essentially fail as it will quickly loop through it's afforded tries. This is not clear in the documentation, though it's implied with the explanation that an overlapping job will get released back to the queue... I guess it can only be released if it has started. If I am undestanding correctly, WithoutOverlap middleware does not prevent overlap as the documentation says - it ends overlap at the cost of a try.

https://laravel.com/docs/9.x/queues#preventing-job-overlaps

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Answer selected by garrettboone
Comment options

You must be logged in to vote
1 reply
@garrettboone
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants