BerriAI/litellm · error · HTTPException
Failed to get access group info: {e}
Error message
Failed to get access group info: {e} What it means
Catch-all around access-group info retrieval: unexpected exceptions during the DB fetch are logged with the group name and re-raised as this 500. The 404 not-found case is raised separately as an HTTPException and passes through.
Source
Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:571
detail={"error": "Database not connected."},
)
try:
access_groups_map: Final = await get_all_access_groups_from_db(prisma_client=prisma_client)
if access_group not in access_groups_map:
raise HTTPException(
status_code=404,
detail={"error": f"Access group '{access_group}' not found"},
)
return access_groups_map[access_group]
except HTTPException:
raise
except Exception as e:
verbose_proxy_logger.exception("Error getting access group info for '%s': %s", access_group, e)
raise HTTPException(
status_code=500,
detail={"error": f"Failed to get access group info: {e}"},
)
@router.put(
"/access_group/{access_group}/update",
tags=["model management"],
dependencies=[Depends(user_api_key_auth)],
response_model=NewModelGroupResponse,
)
async def update_access_group(
access_group: str,
data: UpdateModelGroupRequest,
user_api_key_dict: UserAPIKeyAuth = Depends(user_api_key_auth),
):
"""
Update an access group's model names.View on GitHub (pinned to 77b7c6c40c)
Solutions
- Check proxy server logs for the underlying exception details.
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:571 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/9c77a5051a0cd901.
Report an issue: GitHub.