Skip to content

feat(ui): show failure reason inline in the queue jobs list - #51

Open
omarzeineddine-ai wants to merge 1 commit into
pontusab:mainfrom
omarzeineddine-ai:feat/queue-jobs-inline-errors
Open

feat(ui): show failure reason inline in the queue jobs list#51
omarzeineddine-ai wants to merge 1 commit into
pontusab:mainfrom
omarzeineddine-ai:feat/queue-jobs-inline-errors

Conversation

@omarzeineddine-ai

Copy link
Copy Markdown

Problem

Closes #31

The needs attention section links straight to a queue's failed job runs, but the list there only shows name/id/status — you have to click into each job to see what actually failed. The global Runs view already renders the truncated failedReason inline on failed rows.

Solution

Render the same inline error treatment in the queue page's job list: failed rows show the truncated failedReason (80 chars, full message on hover via title), styled and truncated identically to the global runs list.

No API changes needed — the queue jobs endpoint already returns failedReason (jobToInfo includes it in both list and full modes), so this is an 8-line UI change reusing the existing pattern.

Verification

  • Seeded a local queue with 5 failing jobs and confirmed GET /api/queues/:name/jobs?status=failed returns failedReason for each row the UI renders.
  • tsc --noEmit, biome check, and the vite UI build all pass.

No unit test added: the change is presentation-only, reusing markup already exercised by the runs page, and the repo has no component test infrastructure.

The 'needs attention' flow lands on a queue's failed jobs, but the list
only showed name/id/status — you had to open each job to see why it
failed. Render the truncated failedReason on failed rows, using the
same treatment as the global runs list.

Closes pontusab#31
@vercel

vercel Bot commented Jul 16, 2026

Copy link
Copy Markdown

@omarzeineddine-ai is attempting to deploy a commit to the Pontus Abrahamsson's projects Team on Vercel.

A member of the Team first needs to authorize it.

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.

Quick error visibility from job runs

1 participant