LiteLLM / LiteLLM

LiteLLM /v1/responses/compact Fails During Fallback with 'Unknown parameter: metadata'

Fix LiteLLM fallback failure when /v1/responses/compact endpoint returns 400 Unknown parameter metadata Includes evidence for LiteLLM troubleshooting demand.

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

Category: LiteLLM
Error signature: /v1/responses/compact fails during router_settings.fallbacks — Unknown parameter: metadata
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 12, 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

/v1/responses/compact fails during router_settings.fallbacks — Unknown parameter: metadata is a LiteLLM failure pattern reported for developers trying to fix litellm fallback failure when /v1/responses/compact endpoint returns 400 unknown parameter metadata. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

/v1/responses/compact fails during router_settings.fallbacks failover from primary to fallback model, with Azure returning 400 'Unknown parameter: metadata'. Hardcoded metadata key in run_async_fallback causes the error.

Common causes

LiteLLM is a widely used API proxy for routing between multiple LLM providers. Fallback failures mean production AI services degrade without proper error handling.
/v1/responses/compact fails during router_settings.fallbacks failover from primary to fallback model, with Azure returning 400 'Unknown parameter: metadata'. Hardcoded metadata key in run_async_fallback causes the error.

Quick fixes

Confirm the exact error signature matches /v1/responses/compact fails during router_settings.fallbacks — Unknown parameter: metadata.
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 /v1/responses/compact fails during router_settings.fallbacks — Unknown parameter: metadata 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 /v1/responses/compact fails during router_settings.fallbacks — Unknown parameter: metadata mean in LiteLLM?

/v1/responses/compact fails during router_settings.fallbacks — Unknown parameter: metadata indicates the workflow described by "LiteLLM /v1/responses/compact Fails During Fallback with 'Unknown parameter: metadata'" failed in a LiteLLM context. Start by confirming the exact signature and the component that emitted it.

What should I check first for /v1/responses/compact fails during router_settings.fallbacks — Unknown parameter: metadata?

Check whether this cause matches your environment: LiteLLM is a widely used API proxy for routing between multiple LLM providers. Fallback failures mean production AI services degrade without proper error handling.

Is the /v1/responses/compact fails during router_settings.fallbacks — Unknown parameter: metadata guidance source-backed?

The "LiteLLM /v1/responses/compact Fails During Fallback with 'Unknown parameter: metadata'" 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 /v1/responses/compact fails during router_settings.fallbacks — Unknown parameter: metadata?

For "LiteLLM /v1/responses/compact Fails During Fallback with 'Unknown parameter: metadata'", 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 /v1/responses/compact fails during router_settings.fallbacks — Unknown parameter: metadata?

For "LiteLLM /v1/responses/compact Fails During Fallback with 'Unknown parameter: metadata'", 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.