[13.x] Surface paused queues in the queue worker output - #61142
Merged
taylorotwell merged 3 commits intoAug 12, 2026
Conversation
|
Thanks for submitting a PR! Note that draft PRs are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface. Pull requests that are abandoned in draft may be closed due to inactivity. |
jackbayliss
marked this pull request as ready for review
August 12, 2026 11:26
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.
Basically, queue pausing and resuming is cool.
But, when you're running a worker, or implementing queue pausing user land it's not 100% clear from the worker side that it is paused.
Currently, that means we get the below (the output just stops...):
Details
Screen.Recording.2026-08-12.at.10.03.28.mov
This PR adds 2 new events for the Worker command listens to.. meaning we get the output:
Details
Screen.Recording.2026-08-12.at.09.55.58.mov
This adds a property to the Worker so it keeps track of its own queues, and means it doesnt get spammed every loop
The coolest part is if a queue is paused and THEN you bring the worker up, it'll still report it as paused
(Hopefully you see the idea)
Happy for you to change it about!