BerriAI/litellm · error · HTTPException
Failed to check access group existence: {e}
Error message
Failed to check access group existence: {e} What it means
Catch-all around the existence pre-check in the access-group update flow: the DB query for existing groups failed with an unexpected error, so the update cannot safely proceed; logged and converted to this 500. The 404 for a genuinely absent group is raised separately.
Source
Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:649
raise HTTPException(
status_code=400,
detail={"error": "Either model_names or model_ids must be provided and non-empty"},
)
use_model_ids: Final = has_model_ids
# Validation: Check if access group exists
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"},
)
except HTTPException:
raise
except Exception as e:
raise HTTPException(
status_code=500,
detail={"error": f"Failed to check access group existence: {e}"},
)
# Validation: Check if all new models exist (only if using model_names path)
if not use_model_ids and has_model_names:
assert data.model_names is not None
all_valid, missing_models = validate_models_exist(
model_names=data.model_names,
llm_router=llm_router,
)
if not all_valid:
raise HTTPException(
status_code=400,
detail={"error": f"Model(s) not found: {', '.join(missing_models)}"},
)
View on GitHub (pinned to 77b7c6c40c)
Solutions
- Check proxy server logs for the underlying exception details.
- Verify database connectivity.
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:649 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/d44a3060af588644.
Report an issue: GitHub.