Skip to main content
POST
Reschedule a job

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

job_id
string<uuid>
required

Unique identifier for a job.

Body

application/json

Optional body for rescheduling a job. May be omitted entirely — an empty body keeps the default behavior, where rescheduling is a no-op for jobs already in a terminal state (completed, cancelled, failed).

force
boolean
default:false

When true, reschedule the job even if it is in a terminal state, resetting it to pending and clearing its executor so the operator re-dispatches it onto a fresh cluster. Use this to re-run a job that already finished. When omitted or false, terminal jobs are left untouched.

Response

OK

Result of rescheduling a job — what happened, plus the job's current state afterwards.

outcome
enum<string>
required

What a reschedule call did.

  • rescheduled — the job was put back on the queue (reset to pending, executor cleared).
  • skipped_terminal — the job was left untouched because it was already in a terminal state and force was not set.
Available options:
rescheduled,
skipped_terminal
job
object
required
Example: