Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Side queries retry in more cases with a fixed dispatch value

Side queries now resend once with a fixed dispatch value after a headerless 503 or a 408, 409 or 429, and API results record a dispatch value

Group of 2 Under the hood Internal Changes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release

What

A side query is a smaller background request Claude Code sends to the model alongside the main conversation. Some requests carry a dispatch header, a label that tells the service how to route them. When a side query fails, it can now be sent again once with a fixed dispatch value in three cases:

  • headerless_decline: an HTTP 503 error on a request that was sent without a dispatch header.
  • Server or connection errors: a 5xx error or a connection failure. This case existed before.
  • retryable_4xx: HTTP 408, 409 or 429. These are resent using the client's usual retry allowance, unless the server marked its requested wait (Retry-After) as too long. Before, these codes were resent only when a header had been sent.

The record of a fallback resend now includes resend_dispatch. The records Claude Code keeps for successful and failed API calls now include a dispatch value, which defaults to none.

Why

Side queries are more likely to succeed when the routing layer turns a request down, instead of failing outright. The added dispatch value is diagnostic information and changes nothing you do.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what `dispatch` records.

See this entry in the whole of v2.1.281 →

Feedback