Error · 504

upstream_timeout

An upstream system timed out

What happened

An upstream system did not respond in time.

What to do

Retry after a short pause. If it persists, the upstream is degraded.

The response body carries a recovery object with the same guidance in machine-readable form: recovery.action names the call to make next, and recovery.hint is one sentence a model can act on. Not every code carries one — a 401, for instance, has nothing to recover to but a valid token.

Back to the full error reference

504 application/problem+json

{9 keys}

:"https://api.inleed.com/errors/upstream_timeout",

:"An upstream system timed out",

:504,

:"An upstream system did not respond in time.",

:"upstream_timeout",

:"/api/v1/…",

:"req_01hxa3b4c5d6e7f8g9h0j1k2m3",

:"2026-08-29T12:34:56.000Z",

:{2 keys}

:"…",

:"Retry after a short pause. If it persists, the upstream is degraded."

}

Click a key to copy its jq path.

Handling it

// Branch on code, never on title or detail — those are written for
// humans and may change wording at any time.

if (problem.code === 'upstream_timeout') {
  // Retry after a short pause. If it persists, the upstream is degraded.
}