{"version":"2.1.284","anchor":"api-error-telemetry-records-whether-non-streaming-fallback-w","canonical_anchor":"api-error-telemetry-records-whether-non-streaming-fallback-w","heading":"API error reports now note whether the non-streaming fallback was skipped","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/api-error-telemetry-records-whether-non-streaming-fallback-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### API error reports now note whether the non-streaming fallback was skipped\n\nClaude Code's API error reports now record whether it skipped its non-streaming fallback, a retry path for failed streamed replies\n\n**Unclear.** What causes the fallback to be skipped is not clear.\n\n**What**\n\nWhen a request to the API fails, Claude Code records an error report. That report now also notes whether the non-streaming fallback was skipped. The non-streaming fallback is a second way of fetching a reply when the streamed, word-by-word reply fails.\n\n**Why**\n\nThere is now a path where Claude Code can skip that fallback.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}