renza

Errors

resource_already_exists

Returned as conflict_error with HTTP 409.

What happened

Creating this resource collided with one that already exists (a uniqueness constraint).

How to fix it

Fetch the existing resource instead, or use upsert-by-`external_id` semantics so a repeat create becomes an update.

The envelope

{
  "error": {
    "type": "conflict_error",
    "code": "resource_already_exists",
    "message": "",
    "request_id": "req_8f2c4a1b",
    "doc_url": "https://docs.renza.io/errors/resource_already_exists"
  }
}

See Errors for the full contract, and note the CLI maps this to a stable exit code — see Output & exit codes.