# conflict

<Badge variant="warning">409 Conflict</Badge> <Badge variant="muted">conflict</Badge>

| Field | Value |
|---|---|
| **Type URI** | `https://docs.kordiam.app/docs/errors/conflict` |
| **HTTP Status** | `409 Conflict` |

## Description
The request conflicts with the current state of the target resource. The operation cannot be completed until the conflict is resolved.

## Response Example
```json
{
  "type": "https://docs.kordiam.app/docs/errors/conflict",
  "title": "Conflict",
  "status": 409,
  "detail": "A resource with the same unique identifier already exists.",
  "instance": "/api/v2/elements",
  "traceId": "abc-123-def"
}
```

## Common Causes
- A resource with the same unique value already exists (e.g., a duplicate name or identifier).
- The requested state transition is not allowed given the resource's current state.

## How to Fix

1. Retrieve the current state of the resource to understand the conflict.
2. For uniqueness violations, use a different value for the conflicting field or update the existing resource instead.
3. For state transition conflicts, verify the resource is in a valid state for the intended operation before retrying.