api_key_roll_conflict
This key was rolled concurrently; this roll did not land.
This key was rolled concurrently; this roll did not land.
| Code | api_key_roll_conflict |
| Type | conflict_error — State conflict |
| HTTP | 409 |
| Retriable? | Yes |
What to do
Another roll of the same key won the race, and ITS secret is the live one — the response you are reading carries none. Fetch the key again and roll once if you still need to.
Retrying the same request may work. Respect Retry-After when it comes.
The envelope
{
"error": {
"type": "conflict_error",
"code": "api_key_roll_conflict",
"message": "…",
"hint": "Another roll of the same key won the race, and ITS secret is the live one — the response you are reading carries none. Fetch the key again and roll once if you still need to.",
"retriable": true,
"doc_url": "https://docs.facturia.cl/errors/api_key_roll_conflict",
"request_id": "req_01K2R7Q9M4T2VB"
}
}Program against code, never against message — the prose can be rewritten, the code cannot (§5.8).
hint and retriable arrive in the response with these exact values: they are a function of code and come from the same dictionary GET /v1/error_codes serves, so the envelope and the dictionary cannot disagree. Both are English on the wire by design — one registry, one language. More in The error envelope.
See also
Every code
The error envelope
The machine-readable copy of this page lives at GET /v1/error_codes, unauthenticated.