timeout

HTTP status: 504

A downstream service call exceeded its configured deadline and the request was abandoned. The operation did not complete.

Retry with the same idempotency key to avoid duplicate operations.

Why this happens

• A carrier underwriting service is experiencing elevated latency.
• A database query ran longer than its deadline during high load.
• The server is under load and a normally fast operation is queueing behind slower ones.

What to do

1. Retry the request with the same idempotency key. The server will either:
   • Process the request and return the result, or
   • Return the cached result if an earlier attempt completed behind the scenes.
2. Do not generate a new idempotency key on retry — doing so may create duplicate operations.
3. The SDK auto-retries 504 with the same key. If you are calling the API directly, reuse the key.
4. If retries consistently fail, check support-and-status for active incident communications.

Example response

{
  "type": "https://zyins.isaapi.com/errors/timeout",
  "title": "Upstream timeout",
  "status": 504,
  "detail": "A downstream service call exceeded its 10-second deadline. Retry with the same Idempotency-Key.",
  "code": "timeout",
  "advice_code": "retry_same_key",
  "param": null,
  "request_id": "req_01HZK2N5GQR9T8X4B6FJW3Y1AS"
}

SDK exceptions

See also

• Error catalog
• Idempotency guide
• Support and status