Skip to main content
POST
POST /v1/training/jobs/{job_id}/stop Stops a running job and preserves checkpoints created before the stop. For an interactive job, the request returns immediately and rejects new training calls. Already queued training operations may finish before resources are released, and usage may continue until that release. Sampling from saved sampler checkpoints remains available after the stop.

Request

string
required
Your Fastino API key.
string
required
Config-job UUID or interactive job ID.

Config job

The JSON body is optional for a config job.
string
Why the job was stopped.
object
Numeric metrics used to make the stop decision.
string
Checkpoint path or step associated with the stop.

Interactive job

Send no request body. The response includes the verified common fields success, job_id, and status.

Config-job request example

Interactive-job request example

Config-job response

The message field, 202 response, and polling rule apply only to config jobs. Poll GET /v1/training/jobs/{job_id} after a config-job 202; do not repeat the stop request while cancellation is pending.

Interactive-job response

An interactive job uses the same operation without a body. It returns the common fields success, job_id, and status. Do not require the config-only message field from an interactive response.
Response

Config-job statuses

The following statuses and error details apply only to config jobs.

Config-job authorization

For config jobs, this operation requires the Owner, Admin, or Editor team role. Other roles receive 403 Forbidden. The native interactive handler uses the interactive runtime’s caller authorization; do not infer config-job RBAC from this shared path.