Repository navigation
docs: clarify queue timeout and retry behavior - #1290
Open
outdooracorn wants to merge 1 commit into
Open
outdooracorn wants to merge 1 commit into
outdooracorn wants to merge 1 commit into
Conversation
Document how job-level settings override queue-worker defaults and explain the required relationship between job timeouts and retry_after. The `'retry_after' => 100,` value in `config/queue.php` should be changed in a follow-up commit to be greater than the longest job timeout. Bug: T440406
outdooracorn
added this pull request to stack #1291
October 6, 2026 21:49
outdooracorn
commented
Oct 8, 2026
Comment on lines
+198
to
+199
| // A job's `$timeout` property takes precedence over this default. | ||
| // https://laravel.com/framework/docs/11.x/queues#timeout |
Member
Author
There was a problem hiding this comment.
Looking at the Laravel 12.x Horizon docs, I don't think this is correct. Seems like the Horizon timeout is separate from the Job timeout. Either something has changed between 11.x and 12.x or the documentation has been improved and I got this wrong first time round.
I'll investigate further and update.
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.
Document how job-level settings override queue-worker defaults and explain the required relationship between job timeouts and retry_after.
The
'retry_after' => 100,value inconfig/queue.phpshould be changed in a follow-up commit to be greater than the longest job timeout.Bug: T440406
Stack created with GitHub Stacks CLI • Give Feedback 💬