{"version":"2.1.261","anchor":"new-no-response-diagnostic-field-for-stream-timeouts","canonical_anchor":"new-no-response-diagnostic-field-for-stream-timeouts","heading":"New no_response diagnostic field for stream timeouts","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/new-no-response-diagnostic-field-for-stream-timeouts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### New no_response diagnostic field for stream timeouts\n\nTelemetry schema now records how long a no-response stream timeout waited.\n\nThe retry\/error telemetry schema gained an optional `no_response` object with `waited_ms` and `retry_wait_ms` fields, populated only when the API sent no response headers within the first-byte timeout window (`CLAUDE_STREAM_FIRST_BYTE_TIMEOUT_MS`). This distinguishes a no-response timeout from a normal retry, reporting how long the failed attempt waited for headers and how long the retry will wait.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}