Check for existing issues

• I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

When calling /team/member_update with max_budget_in_team, the _upsert_budget_and_membership function always creates a new budget row via litellm_budgettable.create. The member's team_membership is then connected to the new budget. However, the previous budget row is never deleted, leaving orphaned rows in litellm_budgettable.

Creating a new individual budget when explicitly overriding a member's value is correct, it properly detaches them from a shared budget. The issue is purely that the old budget row is left behind.

Repeatedly calling member_update for the same member (e.g., adjusting their budget multiple times) creates a new orphaned row each time.

Expected behavior: The previous budget row should be cleaned up (deleted) when a new one is created and linked, unless it is still referenced by other memberships.

Actual behavior: Old budget rows accumulate in litellm_budgettable with no references.

Steps to Reproduce

1. Create a team with a member budget and add a member:

   curl -X POST http://localhost:4000/team/update \
     -H "Authorization: Bearer sk-admin" \
     -H "Content-Type: application/json" \
     -d '{"team_id": "1", "team_member_budget": 2.0, "team_member_budget_duration": "30d"}'
   
   curl -X POST http://localhost:4000/team/member_add \
     -H "Authorization: Bearer sk-admin" \
     -H "Content-Type: application/json" \
     -d '{"team_id": "1", "member": {"user_id": "user-A", "role": "user"}}'

2. Note the member's budget_id from GET /team/info?team_id=1 (e.g., team-...-budget-abc)
3. Update the member's budget:

   curl -X POST http://localhost:4000/team/member_update \
     -H "Authorization: Bearer sk-admin" \
     -H "Content-Type: application/json" \
     -d '{"team_id": "1", "user_id": "user-A", "max_budget_in_team": 5}'

4. Note the member now has a new budget_id (e.g., 59db2fc6-...). The old budget row (team-...-budget-abc) still exists in litellm_budgettable but is no longer referenced by this member.
5. Repeat step 3 multiple times, each call creates another orphaned budget row.

Relevant log output

No relevant log files. Maybe a JSON representation of /team/info helps with understanding.

# Before member_update
{ "user_id": "user-A", "budget_id": "team-budget-abc", "litellm_budget_table": { "max_budget": 2.0 } }

# After first member_update
{ "user_id": "user-A", "budget_id": "59db2fc6-...", "litellm_budget_table": { "max_budget": 5.0 } }
# budget row "team-budget-abc" still exists in DB (orphaned if no other members reference it)

# After second member_update
{ "user_id": "user-A", "budget_id": "a1b2c3d4-...", "litellm_budget_table": { "max_budget": 8.0 } }
# budget rows "team-budget-abc" AND "59db2fc6-..." now both orphaned

What part of LiteLLM is this about?

Proxy

What LiteLLM version are you on ?

v1.83.3.rc.1

Twitter / LinkedIn details

No response