502
Retry with backoffAPI temporarily unreachable — The proxy in front of the API could not reach it for a moment — usually during a deploy. Transient.
Response body
{ "error": { "code": "upstream_unavailable", … } }
Should you retry?
Yes — with exponential backoff, and honour Retry-After
when it is present.
What it means
The request never reached the API, so nothing was served or billed. This one is answered by the proxy in front of the API rather than the API itself, but in the same envelope, with an X-Request-Id and a Retry-After header. A 502 (or 503) with no JSON body came from the load balancer further out; treat it exactly the same way.
Common causes
- A deploy or restart on JobFront's side.
- A sudden burst of traffic that briefly filled the API's queue.
How to fix it
Retry with exponential backoff, starting at Retry-After seconds. It usually clears within seconds. If it persists for more than a few minutes, check jobfront.com/status and send us the request_id.