[13.x] Support Concurrency Run Timeouts#60105
Merged
taylorotwell merged 1 commit intoMay 13, 2026
Merged
Conversation
- add optional timeout arguments to concurrency run contracts - apply custom timeouts to process driver pool commands - document facade timeout usage and cover process behavior
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
2 participants
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.
Concurrency::run()currently uses the process driver by default, where each task is executed through Laravel’s process layer. That process layer has a default 60-second timeout, butConcurrency::run()did not expose a way to customize it.This PR adds support for passing a custom timeout when using the process driver:
The fork driver is left unchanged because
spatie/forkdoes not support task timeouts. The sync driver also keeps its existing behavior, since it runs tasks inline and a process timeout would not apply.