You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
TelemetryArea: what it touches
ImprovementsKind: in v2.1.265,
ImprovementsSection of the release
What
When Claude Code sends telemetry (OTEL) data to an external destination and gets back an HTTP 400, 413, 415, 422, or 431 response, it's now treated as the destination rejecting the payload itself, rather than a connection or service failure. This is logged, but only roughly once every 100 occurrences, and it no longer counts toward the circuit breaker (the mechanism that temporarily stops sending to a failing destination). Other kinds of failures still count and can still trip the breaker, taking the destination offline for 30 seconds.
Why
This stops a destination that's rejecting malformed or unexpected payloads from being mistakenly treated as unreachable and temporarily cut off, while still protecting against destinations that are genuinely failing.
