Skip to main content

conformance_unavailable

HTTP 503 · code: "conformance_unavailable" · type: https://docs.formfeed.dev/errors/conformance-unavailable

The service that turns a rendered PDF into an e-invoice and validates it, and that validates a file rendered with pdf.ua, is busy or not reachable right now. Where a second attempt could help, Formfeed has already made it. A render that asked for an e-invoice never comes back as a plain PDF instead, and one that asked for PDF/UA-1 never comes back unchecked: you get the validated file or this problem. The answer carries Retry-After (5 seconds). Nothing was charged.

Example​

{
  "type": "https://docs.formfeed.dev/errors/conformance-unavailable",
  "title": "Conformance service unavailable",
  "status": 503,
  "detail": "The conformance service is not reachable; retry shortly",
  "code": "conformance_unavailable",
  "render_id": "rnd_7da09ab6cd9946b798c187c2a9350852",
  "request_id": "req_4b7c1e9a2f3d4c5b8a6e7f9012"
}

Common causes​

  • Many e-invoices or PDF/UA files at the same time in your region. Each file is converted or validated on its own, so bursts queue up (The conformance service is busy; retry shortly).
  • The service restarting after an update (The conformance service is not reachable; retry shortly).
  • A region in which e-invoices or the PDF/UA check are not available (E-invoices are not available in this region, PDF/UA validation is not available in this region).

A conversion or validation that takes longer than its 20 seconds answers render_timeout instead.

How to fix it​

  • Retry after the number of seconds in the Retry-After header, with the same Idempotency-Key.
  • Send large numbers of documents as async renders or a batch: the queue retries this failure by itself, 5 and then 10 seconds later. When all three attempts fail, the render fails as worker_exhausted, with this code's message in detail.
  • If it keeps happening, send the request_id to support@formfeed.dev.

Retry?​

Yes, after Retry-After seconds, with the same Idempotency-Key; answers of 503 are not stored under the key. The SDKs do this for you.