BerriAI/litellm · error · HTTPException

Access group '{access_group}' not found

Error message

Access group '{access_group}' not found

What it means

Lookup guard on GET /access_group/{access_group}/info: the name is absent from the map returned by get_all_access_groups_from_db, so no group with that exact name exists. Case-sensitive match; 404 returned.

Source

Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:560

    Returns:
    - AccessGroupInfo with the access group details
    
    Raises:
    - HTTPException 404: If access group not found
    """
    from litellm.proxy.proxy_server import prisma_client

    if prisma_client is None:
        raise HTTPException(
            status_code=500,
            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",

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Verify the access group name. List groups via the list endpoint to find valid names.

When it happens

Trigger: Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:560 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/3612b7cd89856268. Report an issue: GitHub.