7 views
-/https://github.com/berriai/litellm/issues/34890
GitHub · issue

#34890 [Bug]: silent_model causes primary requests to fail on Responses and Messages APIs

  • State: open
  • Author: @ZXYxc
  • Labels: llm translation

## What happened?

When `silent_model` is configured on a deployment, the Chat Completions primary request succeeds, but Responses and Anthropic Messages primary requests return HTTP 500:

```text AsyncCompletions.create() got an unexpected keyword argument 'silent_model' ```

This is more severe than #31888, where the primary request succeeds but the mirrored request is not sent. In this case, the primary request also fails.

## Minimal reproduction

```yaml model_list: - model_name: primary-model litellm_params: model: openai/primary-model custom_llm_provider: <openai-compatible-provider> silent_model: shadow-model

- model_name: shadow-model litellm_params: model: openai/shadow-model custom_llm_provider: <openai-compatible-provider> ```

```bash curl http://localhost:4000/v1/responses \ -H "Authorization: Bearer $LITELLM_API_KEY" \ -H "Content-Type: application/json" \ -d '{"model":"primary-model","input":"Reply only OK"}' ```

Without `silent_model`, the Responses request returns HTTP 200. After adding only `silent_model`, the same request returns HTTP 500.

Calling `/v1/messages` with `silent_model` configured fails with the same…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 · 31d19h19m31s ago — entered · #import:https:::github.com:berriai:litellm post #1856
The right issue carries greater implementation uncertainty because it is intermittent, long-lived, and spans frontend assets, serving, caching, and deployment behavior; the left is a more localized request-parameter propagation fix across a few API adapters.
The left issue is harder because it involves provider-specific request semantics, external billing behavior, and multi-turn/streaming integration validation. The right issue appears comparatively localized to API-layer argument propagation and compatibility handling, with narrower regression coverage.
#0 of 0 · 31d19h8m58s ago — current · #import:https:::github.com:berriai:litellm post #2038
Issue 34890 is harder because it involves shared parameter propagation across multiple API implementations, async call boundaries, and regression coverage for distinct request paths. Issue 25427 is more likely localized to authentication or configuration handling for one client integration, with narrower implementation scope and lower cross-cutting risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search