job_not_resumable
409 Conflict This job cannot be resumed.
When you get it
This job cannot be resumed. 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.
reason- The machine-readable sub-case, when one code covers several. Branch on it.
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-resumable",
"title": "This job cannot be resumed.",
"status": 409,
"code": "job_not_resumable",
"errors": [
{ "state": …, "reason": … }
]
}