BerriAI/litellm · error · Exception
Error getting agent from DB: {e}
Error message
Error getting agent from DB: {e} What it means
Except-handler in get_agent: an unexpected error escaped while searching the in-memory list / legacy-id map; the message wraps the underlying exception, usually indicating a registry state bug rather than a missing agent.
Source
Thrown at litellm/proxy/agent_endpoints/agent_registry.py:586
"""
Get an agent by its ID from the database
"""
try:
for agent in self.agent_list:
if agent.agent_id == agent_id:
return agent
translated_id: Final = self.config_agent_legacy_ids.get(agent_id)
if translated_id is None:
return None
for agent in self.agent_list:
if agent.agent_id == translated_id:
return agent
return None
except Exception as e:
raise Exception(f"Error getting agent from DB: {e}")
def get_agent_by_name(self, agent_name: str) -> AgentResponse | None:
"""
Get an agent by its name from the database
"""
try:
for agent in self.agent_list:
if agent.agent_name == agent_name:
return agent
return None
except Exception as e:
raise Exception(f"Error getting agent from DB: {e}")
global_agent_registry: Final = AgentRegistry()
View on GitHub (pinned to 77b7c6c40c)
Solutions
- Check database connectivity and that the agent exists.
Example fix
Verify DATABASE_URL and agent ID.
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at litellm/proxy/agent_endpoints/agent_registry.py:586 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of BerriAI/litellm@77b7c6c40c (2026-08-18).
Data as JSON: /api/errors/b7ad891fbd5fd9db.
Report an issue: GitHub.