### Check for existing issues

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

### What happened?

Hi,

We're seeing an issue in a distributed setup where responses occasionally seem to be returned to the wrong client.

Environment

- OpenShift (multiple replicas) - Image: litellm-database (v1.81.3+) - Redis Cluster enabled - Behavior

Under concurrent load, it looks like a response generated for one request is sometimes returned to another client.

We noticed this happens more often when multiple sessions are using the same API key.

Question: Is there any known limitation or configuration requirement when using LiteLLM with: Redis Cluster Multiple replicas Shared API keys

Specifically, could this be related to caching or request scoping?

Would appreciate guidance on the correct configuration to ensure proper isolation between requests.

Thanks!

### Steps to Reproduce

.

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

Proxy

### What LiteLLM version are you on ?

v1.81.3

### Twitter / LinkedIn details

_No response_