Error · 409

conflict

The request conflicts with the current state

What happened

The request conflicts with the current state of the resource.

What to do

Re-read the resource, then retry against its new state.

The response body carries a recovery object with the same guidance in machine-readable form: recovery.action names the call to make next, and recovery.hint is one sentence a model can act on. Not every code carries one — a 401, for instance, has nothing to recover to but a valid token.

hosting_not_ready — The hosting account is not ready yet
attempt_replayed — This attempt key has already been used
quota_exceeded — Quota exceeded
shell_not_enabled — Shell access is not enabled for this account

Back to the full error reference

409 application/problem+json

{9 keys}

:"https://api.inleed.com/errors/conflict",

:"The request conflicts with the current state",

:409,

:"The request conflicts with the current state of the resource.",

:"conflict",

:"/api/v1/…",

:"req_01hxa3b4c5d6e7f8g9h0j1k2m3",

:"2026-08-29T12:34:56.000Z",

:{2 keys}

:"…",

:"Re-read the resource, then retry against its new state."

}

Click a key to copy its jq path.

Handling it

// Branch on code, never on title or detail — those are written for
// humans and may change wording at any time.

if (problem.code === 'conflict') {
  // Re-read the resource, then retry against its new state.
}

What happened

What to do

Other 409 responses