LiteLLM / LiteLLM

LiteLLM Bedrock Pass-Through Returns 200 with Empty Body on v1.85.0

After upgrading to LiteLLM v1.85.0, AWS Bedrock proxy requests return HTTP 200 but with empty response body — clients receive success status but no content; silent data loss affecting production inference pipelines Includes evidence for LiteLLM troubleshooting demand.

Source-backed Last updated May 21, 2026 1 source Needs local verification

Category: LiteLLM
Error signature: [Bug]: Bedrock pass-through /converse returns 200 with empty body on v1.85.0
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 21, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for LiteLLM, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

[Bug]: Bedrock pass-through /converse returns 200 with empty body on v1.85.0 is a LiteLLM failure pattern reported for developers trying to after upgrading to litellm v1.85.0, aws bedrock proxy requests return http 200 but with empty response body — clients receive success status but no content; silent data loss affecting production inference pipelines. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #28388 on BerriAI/litellm opened May 26, 2026 by luiz-berto. Labels: bug, llm translation, proxy. A regression in v1.85.0 where the Bedrock passthrough layer fails to forward the actual API response body while still returning 200 OK. This silent failure pattern is particularly dangerous for production systems that won't detect the error. Category: LiteLLM (direct mapping).

Common causes

GitHub issue #28388 on BerriAI/litellm opened May 26, 2026 by luiz-berto. Labels: bug, llm translation, proxy. A regression in v1.85.0 where the Bedrock passthrough layer fails to forward the actual API response body while still returning 200 OK. This silent failure pattern is particularly dangerous for production systems that won't detect the error. Category: LiteLLM (direct mapping).

Quick fixes

Confirm the exact error signature matches [Bug]: Bedrock pass-through /converse returns 200 with empty body on v1.85.0.
Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match [Bug]: Bedrock pass-through /converse returns 200 with empty body on v1.85.0 exactly before applying the quick fix.
Compare the failing environment with LiteLLM versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does [Bug]: Bedrock pass-through /converse returns 200 with empty body on v1.85.0 mean in LiteLLM?

[Bug]: Bedrock pass-through /converse returns 200 with empty body on v1.85.0 indicates the workflow described by "LiteLLM Bedrock Pass-Through Returns 200 with Empty Body on v1.85.0" failed in a LiteLLM context. Start by confirming the exact signature and the component that emitted it.

What should I check first for [Bug]: Bedrock pass-through /converse returns 200 with empty body on v1.85.0?

Check whether this cause matches your environment: GitHub issue #28388 on BerriAI/litellm opened May 26, 2026 by luiz-berto. Labels: bug, llm translation, proxy. A regression in v1.85.0 where the Bedrock passthrough layer fails to forward the actual API response body while still returning 200 OK. This silent failure pattern is particularly dangerous for production systems that won't detect the error. Category: LiteLLM (direct mapping).

Is the [Bug]: Bedrock pass-through /converse returns 200 with empty body on v1.85.0 guidance source-backed?

The "LiteLLM Bedrock Pass-Through Returns 200 with Empty Body on v1.85.0" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for [Bug]: Bedrock pass-through /converse returns 200 with empty body on v1.85.0?

For "LiteLLM Bedrock Pass-Through Returns 200 with Empty Body on v1.85.0", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging [Bug]: Bedrock pass-through /converse returns 200 with empty body on v1.85.0?

For "LiteLLM Bedrock Pass-Through Returns 200 with Empty Body on v1.85.0", collect the failing LiteLLM command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.