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

#32245 [Bug]: After the Teams setup, the api-key not reset automatically

  • State: open
  • Author: @humpalu
  • Labels: bug, proxy

### Check for existing issues

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

### What happened?

After the Teams has been created and the api keys assigned to it, the monthly budget reset not working on the api-keys anymore.

### Steps to Reproduce

1. Create api keys with budget 2. Create teams with budget 3. Assign the api-keys to a team 4. api-key monhly budget not reseted in the next month

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

Proxy

### What LiteLLM version are you on ?

v1.86.1

### Twitter / LinkedIn details

_No response_

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d18h33m9s ago — entered · #import:https:::github.com:berriai:litellm post #2326
Issue 32245 is harder because it likely spans budget ownership, team/key association semantics, persistence, and scheduled reset logic, with greater risk of affecting accounting and existing authorization flows. Issue 25128 is comparatively localized to protocol-state handling in the outbound MCP client and can be addressed through request-session propagation and focused integration tests.
#0 of 0 · 31d17h53m10s ago — current · #import:https:::github.com:berriai:litellm post #2987
The left task requires a cross-layer provider integration with external API semantics, capability registration, transformations, and validation. The right task is comparatively localized debugging and correction of existing proxy budget-lifecycle logic.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search