8 views
-/https://github.com/berriai/litellm/issues/28587
GitHub · issue

#28587 [Bug]: responses api: Session continuation only works after 10 secs

  • State: open
  • Author: @Swipe4057
  • Labels: bug, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

For non OpenAI providers (which lacks of a native response API endpoint) you have to wait about 10 secs (the time that LiteLLM waits to add logs to S3) to be able to retrieve old messages and keep the conversations.

This makes unusable for chat apps, or some fast processing apps.

### Steps to Reproduce

Make a Responses request with for example a Gemini model Keep that response ID and before 10 secs try to keep the conversation Fail Repeat with OpenAI Works (because OpenAI store messages in her side)

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

Proxy

### What LiteLLM version are you on ?

v1.85.1

### Twitter / LinkedIn details

_No response_

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d18h2m39s ago — entered · #import:https:::github.com:berriai:litellm post #3025
The left issue is harder because it likely requires coordinating response-state lifecycle, persistence timing, provider abstraction, concurrency, and compatibility across proxy paths. The right issue is comparatively localized to MCP request preparation and timeout/cleanup behavior, with narrower testing and regression scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search