version_conflict (409)

← Error reference

version_conflict

HTTP status: 409

Retryable: Yes — the request did not change server state.

Optimistic concurrency check failed.

When it fires

A `PATCH` or `DELETE` was issued with an `If-Match` version that no longer matches the resource's current version, indicating a concurrent update.

How to handle it

Re-read the resource to obtain the current `version` field, merge your changes, and retry with the new value in `If-Match`. Backoff is unnecessary — there is no rate limit to wait out.

Example response

{
  "error": {
    "type": "https://docs-dev.autohost-dev.uk/api/errors/version_conflict",
    "code": "version_conflict",
    "message": "Resource was modified since your last read",
    "request_id": "req_01HEXAMPLE0000000000000000",
    "doc_url": "https://docs-dev.autohost-dev.uk/api/errors/version_conflict",
    "details": {
      "current_version": 7
    }
  }
}