You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A bug happened!
The default team interface for virtual keys has an issue where, after successfully creating a key in the default team, logging out causes the key to disappear from the default team. However, attempting to create a key with the same name again results in an error stating that a key with the same name already exists.
If a new team is created in advance, and the key is created within this new team instead, the issue does not occur, and the key remains available upon re-login.
Create Key:
re-login:
Relevant log output
No response
Are you a ML Ops Team?
No
What LiteLLM version are you on ?
v1.56.4
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered:
based on the error, it appears the key exists in the db
krrishdholakia
changed the title
[Bug]: The issue lies in the default team’s keys not being persisted in the database.
[Bug]: ui not rendering keys upon relogin
Jan 3, 2025
What happened?
A bug happened!
The default team interface for virtual keys has an issue where, after successfully creating a key in the default team, logging out causes the key to disappear from the default team. However, attempting to create a key with the same name again results in an error stating that a key with the same name already exists.
If a new team is created in advance, and the key is created within this new team instead, the issue does not occur, and the key remains available upon re-login.
Create Key:
re-login:
Relevant log output
No response
Are you a ML Ops Team?
No
What LiteLLM version are you on ?
v1.56.4
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: