Repository navigation
Conversation
Adds more detail about sequences to the job detail page in River UI. It'll show information like the sequence that the job is a member of, the reason the current job is waiting, the sequence head, and the next pending job. This is done at the request of one of our Pro users, who found that introspectability of sequences as they're currently implemented is lacing. All information is about to hit existing sequences indexes with no new migrations needed. With 1.1 million synthetic jobs, lookup times were in the range of 0.1-3.3 ms.
The Pro module needs the new sequence queries from this checkout, but standalone module builds resolve the older published UI dependency. Create a local workspace for tests, lint, and the Pro Docker build so they use the checked-out modules without adding release-incompatible replace directives.
Give sequence details explicit text colors so labels and wait reasons remain readable in light and dark themes. Link the changelog entry to PR #739.
brandur
commented
Nov 15, 2026
| COPY --from=build-ui /app/dist ./dist | ||
|
|
||
| # Build both modules from this checkout, including unreleased shared UI queries. | ||
| RUN go work init . ./riverproui |
Collaborator
Author
There was a problem hiding this comment.
Codex keeps finding workarounds like this one to CI passing properly when API changes between UI and Pro UI. This seems to work okay and gets CI to pass, so left it.
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.
🤖 Adds more detail about sequences to the job detail page in River UI.
It'll show information like the sequence that the job is a member of,
the reason the current job is waiting, the sequence head, and the next
pending job.
This is done at the request of one of our Pro users, who found that
introspectability of sequences as they're currently implemented is
lacking.
The queries use existing sequence indexes with no new
migrations needed. With 1.1 million synthetic jobs, lookup times were in
the range of 0.1-3.3 ms for the ordinary cases. A stress case with 100,000
cancelled jobs configured to allow continuation in one sequence took
28 ms, still using indexes.
Screenshots from the seeded demo data:
Halted by a cancelled job
Waiting behind a running job
Waiting for a retry
Multiple blocking jobs
Awaiting sequence scheduling