puesta_en_vivo_pending
The checklist is finished and Facturia has not yet enabled live emission for this empresa.
The checklist is finished and Facturia has not yet enabled live emission for this empresa.
| Code | puesta_en_vivo_pending |
| Type | unprocessable_error — Well formed, but breaks a domain rule |
| HTTP | 422 |
| Retriable? | Yes |
What to do
Nothing is required from you or from your user: the owner-present canary and the per-empresa enablement are ours. Poll GET /v1/empresas/\{id\}/onboarding or subscribe to empresa.onboarding.updated.
Retrying the same request may work. Respect Retry-After when it comes.
The envelope
{
"error": {
"type": "unprocessable_error",
"code": "puesta_en_vivo_pending",
"message": "…",
"hint": "Nothing is required from you or from your user: the owner-present canary and the per-empresa enablement are ours. Poll `GET /v1/empresas/{id}/onboarding` or subscribe to `empresa.onboarding.updated`.",
"retriable": true,
"doc_url": "https://docs.facturia.cl/errors/puesta_en_vivo_pending",
"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.