Skip to main content

tool_unavailable

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

The service that does the work of /pdf/split, /pdf/compress and /pdf/to-image is busy or not reachable right now. Formfeed already tried again within the 60 seconds a tool call has. The answer carries Retry-After (5 seconds) and the render_id of the failed call, which appears in the render log. Nothing was charged.

Example​

{
  "type": "https://docs.formfeed.dev/errors/tool-unavailable",
  "title": "PDF tools unavailable",
  "status": 503,
  "detail": "The PDF tools are busy; retry shortly",
  "code": "tool_unavailable",
  "render_id": "rnd_0d290c45cbeb4554b946bbad1acee87e",
  "request_id": "req_4b7c1e9a2f3d4c5b8a6e7f9012"
}

Common causes​

  • Many tool calls and office conversions at the same time in your region: the two share a service, so bursts queue up.
  • The service restarting after an update (The PDF tools are not reachable; retry shortly).

How to fix it​

  • Retry after the number of seconds in the Retry-After header, with the same Idempotency-Key.
  • Spread large numbers of calls over time.

Retry?​

Yes, after the seconds in Retry-After, with the same Idempotency-Key; answers of 503 are not stored under the key.