Cascades Docs
Sign in to run requests with your own sandbox key. Sign in
View as Markdown Open in Claude Open in ChatGPT Add MCP server OpenAPI JSON OpenAPI YAML
409 Conflict

conflict — Conflict

Message “The request could not be completed.”

What causes it

  • Two writes raced on the same record — for example two simultaneous requests carrying the same `Idempotency-Key`, or a concurrent update that tripped a uniqueness or optimistic-lock check. This comes from the framework with no `details`.

How to fix it

  1. Retry once after a short delay. Reuse the same `Idempotency-Key` where the operation accepts one, so the retry is safe.
  2. Serialise writes to one record on your side rather than issuing them in parallel.

Operations that return it

Any operation can return this code.

See the API reference for the full list of operations.

Example response

HTTP/1.1 409 Conflict · Content-Type: application/json

409 Conflict
{
  "error": {
    "code": "conflict",
    "message": "The request could not be completed.",
    "details": [],
    "request_id": "6f1c2a3e-8d4b-4c5e-9f0a-1b2c3d4e5f60",
    "doc_url": "https://cascades.crscreditapi.com/docs/api/errors/conflict"
  }
}