jobd_events
Retrieve the event stream that explains why jobs behave unexpectedly, such as repeated skips or cancellations. Filter by event type, job ID, project, or source.
Instructions
The broker's event stream — the surface that explains WHY, not just what. /jobs says a job is queued; only this says it has been skipped 400 times because no worker advertises cuda-32gb, or that its dependency was cancelled, or that a watchdog killed it. Filter by since (2h/3d/1w), event type, job_id, project, or source (broker|worker). Use when a job is not doing what you expect and jobd_status alone does not explain it.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| event | No | Filter to one event type. Known types: admission_blocked, auto_preempt, checkpoint_complete, cwd_refused, dispatch_skip, env_scrubbed, job_cancelled, job_completed, job_dispatched, job_orphaned, job_resurrected, job_started, job_submitted, job_uncancelled, jobs_pruned, logs_pruned, reclaim_suppressed, scheduling_timeout, stale_scope_sweep, submit_warning, sweep_warning, version_drift, watchdog_fired, worker_offline, worker_registered, worker_shutdown, worker_stale. Hook-ingested events may carry custom names beyond these. | |
| limit | No | Max rows, newest-last. Broker clamps to 10000. | |
| since | No | Relative window (2h, 3d, 1w) or an ISO-8601 timestamp. Default: all retained. | |
| job_id | No | Only events for this job. | |
| source | No | Which side emitted the event. | |
| project | No | Only events for this project. |