LOCK_NOT_ACQUIRED

HTTP status: 503

What it means

A distributed lock could not be acquired; the operation is safe to retry.

Why it happens

• A concurrency lock (idempotent create, image-cache fill) stayed busy past the wait budget.

How to fix it

• Safe to retry — the operation did not run.

Example

Every non-2xx response uses the same envelope; path (when present) is the exact JSON path of the offending field, and requestId identifies the request in support conversations:

{
  "error": {
    "code": "LOCK_NOT_ACQUIRED",
    "message": "The operation is temporarily locked by another process. Retry shortly.",
    "docsUrl": "https://automotion.dev/docs/errors/lock_not_acquired"
  },
  "requestId": "req_0123456789abcdef0123456789abcdef"
}

See the error index for the full catalog and the API overview for envelope semantics.