Facturiadocs

go_live_not_ready

The certification has not reached the Declaración de Cumplimiento, so there is no go-live decision to take yet.

The certification has not reached the Declaración de Cumplimiento, so there is no go-live decision to take yet.

Codego_live_not_ready
Typeconflict_error — State conflict
HTTP409
Retriable?Yes

What to do

error.details.blocked_on names the step holding the lane up and error.details.next is the call that reports when it moves. Minting a link now would hand a person a page with no decision on it.

Retrying the same request may work. Respect Retry-After when it comes.

The envelope

{
  "error": {
    "type": "conflict_error",
    "code": "go_live_not_ready",
    "message": "…",
    "hint": "`error.details.blocked_on` names the step holding the lane up and `error.details.next` is the call that reports when it moves. Minting a link now would hand a person a page with no decision on it.",
    "retriable": true,
    "doc_url": "https://docs.facturia.cl/errors/go_live_not_ready",
    "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

The machine-readable copy of this page lives at GET /v1/error_codes, unauthenticated.

On this page