Facturiadocs

set_file_unrecognized

The uploaded bytes are not a set de pruebas.

The uploaded bytes are not a set de pruebas.

Codeset_file_unrecognized
Typeunprocessable_error — Well formed, but breaks a domain rule
HTTP422
Retriable?No

What to do

Nothing was stored, deliberately: a portal login page parsed as an empty set would report the empresa as having no casos, which is a different thing from having no set file. Download the .txt again from the SII certification application — a real one opens with a section header naming a NÚMERO DE ATENCIÓN.

Retrying the same request will fail the same way. Change the request, not the frequency.

The envelope

{
  "error": {
    "type": "unprocessable_error",
    "code": "set_file_unrecognized",
    "message": "…",
    "hint": "Nothing was stored, deliberately: a portal login page parsed as an empty set would report the empresa as having no casos, which is a different thing from having no set file. Download the `.txt` again from the SII certification application — a real one opens with a section header naming a NÚMERO DE ATENCIÓN.",
    "retriable": false,
    "doc_url": "https://docs.facturia.cl/errors/set_file_unrecognized",
    "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