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
Unique identifier for the job.
The data plane the job runs on.
failed, cancelled, completed, pending, scheduled, pending_cancellation, running The type associated with the job. Jobs can have a type of nql-forecast or materialize-view.
- Option 1
- Option 2
The internal job executor tied to the job.
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 causes of job failure
The unique ID associated with the job.
The output of a materialized view.
- Option 1
- Option 2
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.
The compute pool associated with the job, if any.

