← all problem types

job_not_cancellable

409 Conflict   This job has already reached a terminal state.

When you get it

This job has already reached a terminal state. It is always answered with HTTP 409 - one code means one status, so a client may key its handling on either.

Fields it carries

Inside each errors[] entry, beside pointer:

state
The lifecycle state the resource is in, which is why the operation was refused.

A field is omitted when the server genuinely does not know it - an absent member is never the same as an empty one.

How to fix it

The request conflicts with the resource's current state. Re-read the resource and decide, rather than retrying blindly.

Shape

{
  "type":   "https://api2.host-tracker.com/problems/job-not-cancellable",
  "title":  "This job has already reached a terminal state.",
  "status": 409,
  "code":   "job_not_cancellable",
  "errors": [
    { "state": … }
  ]
}