Repository navigation
[13.x] Don't fail database queue jobs on concurrency errors while reserving - #62145
Merged
taylorotwell merged 1 commit intoOct 22, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#58978 started failing jobs when reserving them throws, but that also catches temporary errors like SQLite's "database is locked" or deadlocks. The job gets deleted and marked as failed without ever running.
This only fails the job when the exception isn't a concurrency error. Otherwise the transaction rolls back and the worker picks the job up again on the next poll.
laravel-workflow is currently swapping out the database queue connector to work around this.