[10.x] Update Horizon Documentation to reflect the allowed waits config values #9111
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.
After investigation into why our Horizon installs are still reporting long waits after 60 seconds when it's explicitly stated otherwise in the config, we did some further research.
We have seen that the
waits
array in the Horizon config does not accept multiple queues passed with commas, as seen in the code itself (see link below).https://github.com/laravel/horizon/blob/fd5c8957e08419455cce6efdfc8f2c38a812debd/src/Listeners/MonitorWaitTimes.php#L56
Due to this, the documentation seem to be outdated/incorrect and has been updated to reflect both the default wait, which is 60 seconds, and how it would look if you have multiple queues with different wait times to report on.