Background Job Dashboard

An operator console for what the queues are actually doing.

involved Admin & Operations

What it adds

An internal dashboard showing queued, running, and failed work across every queue, with redacted payloads and a narrow set of safe bulk actions.

What your agent is told to do

1
Build one operator view that spans all queues, not a page per queue. Show depth, oldest item age, throughput, and failure counts per queue so a backlog is visible at a glance.
2
Put the whole dashboard behind an explicit operator permission. Queue payloads carry customer data and job arguments frequently contain credentials.
3
Redact payloads before rendering. Maintain a per-job-type allow list of arguments safe to display and hide everything else — an argument is hidden until someone decides it is safe, not the reverse.
4
Distinguish a job's retry attempts from separate enqueues of the same job. Group attempts under one logical item and show the attempt count, or an operator will read a retry storm as real volume.
5
Offer retry, cancel, and discard only for job types explicitly marked as safe for that action, and support bulk operations with a hard cap on the batch size and a confirmation naming the count.
6
Do NOT let the dashboard become the load problem. Poll on a bounded interval, cache aggregate counts, and never scan an entire queue to render a page.
7
The queued/running/stalled/failed state model, per-job user-facing progress, and cancellation semantics are owned by Background Job Progress; read that model here rather than defining a second one.

Edge cases it handles

A queue with hundreds of thousands of entries must paginate over a bounded window; counting the whole queue on every page load will take the backend down.
A job that finishes between rendering and acting on it must fail the action clearly, not retry something already completed.
Bulk retry on a failing job type re-creates the same failure at scale. Warn before retrying a batch whose recent success rate is near zero.
A stalled worker leaves jobs marked running forever. Detect by heartbeat age and label them as stalled rather than showing them as healthy work in progress.
Discarding a job is unrecoverable. Require confirmation naming the job type and count, and record who did it.
Payload redaction must apply to nested arguments and to the failure backtrace, which regularly quotes the arguments back.
If the queue backend is unreachable, the dashboard must say so plainly rather than showing zeroes that read as an idle system.

Definition of done

One view shows depth, age, throughput, and failures for every queue.
Access requires an operator permission and every action is recorded with an actor.
Payload arguments are hidden unless explicitly allow-listed, including inside nested values and backtraces.
Retry attempts are visually distinguished from separate enqueues.
Retry, cancel, and discard are available only for job types marked safe, and bulk actions are capped and confirmed.
Rendering the dashboard never scans a full queue, and a backend outage is shown as an error, not as zero.
The feature matches the existing design system.
No existing functionality is broken.

Related features

Content Reporting

Scheduled Job Monitor

Notification Delivery Failures

How it works

1

Copy the link

Grab the Markdown instruction URL for this feature.
2

Give it to your AI

Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
3

It inspects, then implements

Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.