When using the Bedrock passthrough endpoint (`/bedrock/model/.../invoke-with-response-stream`) and Anthropic returns an overloaded error mid-stream, the LiteLLM gateway logs a full traceback as an unhandled asyncio task exception, and the client sees a generic "Internal server error" with no indication the request should be retried.

This leads to users believing there is something wrong with LiteLLM rather than seeing that the bedrock model is overloaded.

**Note** analysis done with AI.

**What is happening**

Bedrock streaming always opens with HTTP 200. If Anthropic becomes overloaded mid-stream, the error arrives inside the binary event stream — not as an HTTP non-200. After the stream closes, LiteLLM schedules a background task (`asyncio.create_task`) to flush buffered chunks for spend tracking. That task hits the overloaded error event in the buffered bytes and raises `AnthropicError('Overloaded')`. Because there is no `try/except` in `async_flush_passthrough_collected_chunks`, Python drops it as an unhandled task exception.

A secondary issue: `chunk_parser` hardcodes `status_code=500` for all in-stream error events regardless of `error.type` — so even if the exception prop…