{"version":"2.1.271","anchor":"artifact-session-gateway-reads-now-retry-once-on-5xx429408","canonical_anchor":"artifact-session-gateway-reads-now-retry-once-on-5xx429408","heading":"Artifact session-gateway reads now retry once on 5xx\/429\/408","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifact-session-gateway-reads-now-retry-once-on-5xx429408","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Artifact session-gateway reads now retry once on 5xx\/429\/408\n\nReading a shared artifact now retries once automatically after a temporary server error\n\n**What**\n\nWhen Claude Code reads an artifact through its session gateway (the relay that handles shared-artifact traffic) and the read fails with a server error (500 or higher), a rate-limit error (429), or a timeout (408), it now waits and retries the read once before giving up. It honors any `Retry-After` timing the server provides, within a capped limit. This retryable failure is now reported as a distinct \"unavailable\" error, separate from a hard error that means the connection was actively blocked.\n\n**Why**\n\nMany of these failures are brief and transient, so retrying once automatically means a temporary hiccup no longer surfaces as a failure to the user, while still distinguishing genuine outages from a firm network block.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}