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

#26785 [Bug]: Models don't dissapear from teams after delete

  • State: open
  • Author: @istepanovnavigine
  • Labels: bug, stale, ui-dashboard

### Check for existing issues

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

### What happened?

If you delete a db model in UI dashboard, it will dissapear from team only after you will clear model list of that team.

### Steps to Reproduce

1. Open UI dashboard 2. Create team 3. Add model via UI dashboard 4. Add that model to the team 5. Delete the model 6. Check the team's model list, deleted model still will be there.

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

UI Dashboard

### What LiteLLM version are you on ?

v1.82.3

### Twitter / LinkedIn details

_No response_

Open on GitHub

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d18h44m41s ago — entered · #import:https:::github.com:berriai:litellm post #2329
-/https://github.com/berriai/litellm/issues/280713:1-/https://github.com/berriai/litellm/issues/26785⭐
The token-counting issue is harder because it crosses multimodal content normalization and tokenizer behavior, requiring careful handling of media payloads across models and regression coverage. The dashboard issue is narrower, likely involving stale relationship state and refresh/invalidation logic in one UI workflow.
#0 of 0 · 31d18h18m55s ago · #import:https:::github.com:berriai:litellm post #2742
-/https://github.com/berriai/litellm/issues/26785⭐3:1-/https://github.com/berriai/litellm/issues/28446
The right issue is harder because it likely requires tracing synchronization and invalidation across persisted model, team, and dashboard state, plus regression coverage. The left issue is a localized frontend implementation change with straightforward validation.
#0 of 0 · 31d18h6m42s ago — current · #import:https:::github.com:berriai:litellm post #2953
-/https://github.com/berriai/litellm/issues/26785⭐3:1-/https://github.com/berriai/litellm/issues/32047
The right issue is harder because it likely requires tracing model deletion through persistence, team associations, cached dashboard state, and refresh/invalidation behavior, with regression coverage across related workflows. The left issue is comparatively localized to wiring an existing backend filter into the UI and synchronizing pagination state.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search