Gateway Timeout

gateway-timeout · 504

The fallback type for a 504 that has no named type, and no route in the API sends it today.

As with any timeout, the outcome of the operation would be unknown: it may have completed after the response was sent.

This type adds no members to the ones every error carries.

Common causes

  • A 504 raised without a type of its own reached the error handler.

How to fix the call

  • Read the resource back before retrying a write, so a retry doesn't make a second copy.
  • Send an Idempotency-Key with every write; it makes exactly this case safe to retry.
  • Retry with a growing delay, and stop after a few attempts.

Example response

json
{
  "type": "gateway-timeout",
  "title": "Gateway Timeout",
  "status": 504,
  "detail": "The upstream service did not respond in time",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/deployments",
  "method": "POST",
  "instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/deployments",
  "docs": "https://ghaym.me/docs/errors/gateway-timeout"
}