Runs

Every job this deployment has queued, from the scheduler and from operators alike. It cannot say which lane a queued run waits in — a run behind a busy worker and a run in a lane no worker is serving look identical here; Execution lanes tells them apart. Nothing is in flight, so the board is not refreshing — it refreshes itself every 5s while a run is queued or running.

idle

SCHEDULER STATE UNKNOWNThis deployment did not report whether a scheduler is running, so the “Next fire” times below cannot be relied on.

Running

—

Waiting

—

queued behind a worker

Failed (24h)

—

partial counted separately

Succeeded (24h)

—

rows written

Median run (24h)

—

median, not mean — one long backfill drags a mean past anything typical

Oldest wait

—

whether the queue is moving; depth alone does not say

Outcomes, last 24 hours

Loading the last 24 hours

STATUS

0 rows

Schedule runs, newest first
Run		Items	Rows	Took	Origin		Error
Nothing has been queued on this deployment yet The guided setup at /setup enqueues the cold-start chain; every job it starts appears here.