Trigger a health check
Enqueue a health check job for the specified data plane. Optionally target a specific compute pool. Returns the created job.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
Optional compute pool to target for the health check. If omitted, the data plane's default compute pool is used.
Response
Created
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
- Option 10
- Option 11
- Option 12
- Option 13
- Option 14
- Option 15
- Option 16
- Option 17
- Option 18
- Option 19
A job. Every job carries the same envelope of fields — see JobBase — but input and result hold
job-type-specific payloads, so the response is a union over type: pick the branch whose type matches
and you get the typed input and result for that kind of job.
The union is open on purpose. The server stores input and result as arbitrary JSON and never
constrains their shape, so a job type this spec version does not describe — or an old row written before
the current shapes existed — lands in OtherJobResponse, where both fields stay free-form. Treat the
typed branches as a description of what the API sends today, not as a rule it enforces. No branch closes
itself to extra properties, and new job types can appear without a spec change.
result is null in every branch until the job reaches a terminal state.
Unique identifier for the job.
The company the job belongs to.
failed, cancelled, completed, pending, scheduled, pending_cancellation, running Which operator runs the job, e.g. materialized-view-refresh or datasets_execute_select. Finer-grained
than type.
Free-form labels attached to the job.
The internal job executor tied to the job. Null until an executor picks the job up.
The type of the execution cluster to run the job on.
dedicatedruns job on a dedicated cluster.sharedruns job on a shared cluster.
dedicated, shared The unique ID associated with the job.
The timestamp representing when the job was created.
The timestamp representing when the job was updated.
When the job's current attempt started. A job can be retried; each retry is a new attempt, so this advances to the latest one, while created_at stays at the original submission.
Which attempt this is: 1 for the first, increasing by one on each retry.
The timestamp representing when the job finished. Null until the job reaches a terminal state.
materialize-view The data plane the job runs on. Null for jobs not pinned to one.
The compute pool associated with the job, if any.
When the job was taken off the queue. Null while it is still queued.
The id of the workflow that enqueued the job. Null for jobs not enqueued by a workflow.
The id of the workflow run that enqueued the job. Null for jobs not enqueued by a workflow run.

