CONCURRENT_MODIFICATION

The resource was modified by another operation. Please retry.

Category: General


HTTP status	`409` Conflict
Retry	Yes, unchanged

When it happens

Another request changed the same resource while yours was being processed, so yours was rolled back and nothing of it was applied.

Retry the same request after a short delay: the 409 released your Idempotency-Key, so the same key runs it again. If you rebuild the body from the resource's current state first, send it under a new key. On issue and void the conflict is already an answer — another request is issuing or voiding that invoice — so read the invoice instead of retrying.

Retry

Retry the same request unchanged, with the same Idempotency-Key if you sent one. Wait first, and honour the Retry-After header when the response carries it.

Returned by

The operations where this code is most likely. The list is not exhaustive.

Example response

When this error occurs, the API answers 409 Conflict with a JSON body of this shape:

{
  "type": "https://docs.beel.es/errors/CONCURRENT_MODIFICATION",
  "title": "CONCURRENT_MODIFICATION",
  "detail": "The resource was modified by another operation. Please retry.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "CONCURRENT_MODIFICATION",
    "message": "The resource was modified by another operation. Please retry.",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}