Skip to content

Add sequences information to job detail page - #739

Open
brandur wants to merge 3 commits into
masterfrom
sequence-diagnostics
Open

brandur wants to merge 3 commits into
masterfrom
sequence-diagnostics

Conversation

@brandur

@brandur brandur commented Nov 15, 2026 •

Copy link
Copy Markdown
Collaborator

🤖 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

Halted by a cancelled job; job 2002

Waiting behind a running job

Waiting behind a running job; job 1002

Waiting for a retry

Waiting for a retry; job 4002

Multiple blocking jobs

Multiple blocking jobs; job 7003

Awaiting sequence scheduling

Awaiting sequence scheduling; job 6001

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.
Comment thread Dockerfile.pro
COPY --from=build-ui /app/dist ./dist

# Build both modules from this checkout, including unreleased shared UI queries.
RUN go work init . ./riverproui

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@brandur
brandur requested a review from bgentry November 15, 2026 06:42
@bgentry bgentry mentioned this pull request Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant