About this block

Cron Jobs Monitor is the schedule health surface for the production worker pool, with times in UTC. Five recurring jobs render as rows, each carrying the job name, the cron expression in monospace, a human readable cadence and queue, a dot strip of the last twelve runs, the last run timestamp and duration, the next run estimate, and a status Badge. The usage rollup job is failing: its four most recent dots are red and it drops an inline banner explaining that the last runs exited with code 1 after a warehouse timeout, alongside a View logs affordance. The paused weekly digest renders muted with a paused next run.

Jobs are one typed const array, and both statusVariant and runDotClass are Records so status and run outcome map to a Badge weight and a dot colour without extra branching. The failing banner and the muted paused row each read from the status field, so a single value drives the whole row treatment. The footer notes that overlapping runs are skipped and recorded and that three consecutive failures page the owning team.

When to use

Reach for this block on the jobs or scheduling page, wired to your queue backend and scoped to one worker pool. Point the View logs affordance at the run log for the failing job so an on call engineer can read the exit trace without leaving the page.

A natural flow around it on an Application Pro page:

Before

• Status and health
• App shell

After

• Log viewer
• Workflow automation

What you can display

One strong use is the scheduled jobs health board. Other monitor views:

• Queue depth. Add a pending count and oldest job age per queue to watch for backlog.
• Run history. Expand a job into its recent runs with duration and exit code for each.
• Owner view. Group jobs by owning team so each squad sees only the schedules it is paged for.

Tip: the inline failing banner is the incident cue; keep the exit reason in the row so the on call engineer sees why a job broke before opening the logs.