resolucion_verification_not_allowed
The resolución claim cannot be verified right now; `error.details.reason` names the fact that blocks it.
The resolución claim cannot be verified right now; error.details.reason names the fact that blocks it.
| Code | resolucion_verification_not_allowed |
| Type | conflict_error — State conflict |
| HTTP | 409 |
| Retriable? | Yes |
What to do
One of: sandbox, sfg_channel, no_claim, already_verified, refused, in_flight, range_registered, not_ready, no_factura_tipo. Only not_ready and in_flight clear by waiting.
Retrying the same request may work. Respect Retry-After when it comes.
The envelope
{
"error": {
"type": "conflict_error",
"code": "resolucion_verification_not_allowed",
"message": "…",
"hint": "One of: sandbox, sfg_channel, no_claim, already_verified, refused, in_flight, range_registered, not_ready, no_factura_tipo. Only not_ready and in_flight clear by waiting.",
"retriable": true,
"doc_url": "https://docs.facturia.cl/errors/resolucion_verification_not_allowed",
"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.