BerriAI/litellm · error · HTTPException

Failed to update access group: {e}

Error message

Failed to update access group: {e}

What it means

Catch-all around the access-group update transaction: after validation and existence checks pass, any unexpected exception from re-tagging deployments or the DB write is logged and re-raised as this 500.

Source

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

            access_group=access_group,
        )

        verbose_proxy_logger.info(
            "Successfully updated access group '%s' with %s models updated", access_group, models_updated
        )

        return NewModelGroupResponse(
            access_group=access_group,
            model_names=data.model_names,
            model_ids=data.model_ids,
            models_updated=models_updated,
        )

    except HTTPException:
        raise
    except Exception as e:
        verbose_proxy_logger.exception("Error updating access group '%s': %s", access_group, e)
        raise HTTPException(
            status_code=500,
            detail={"error": f"Failed to update access group: {e}"},
        )


@router.delete(
    "/access_group/{access_group}/delete",
    tags=["model management"],
    dependencies=[Depends(user_api_key_auth)],
    response_model=DeleteModelGroupResponse,
)
async def delete_access_group(
    access_group: str,
    user_api_key_dict: UserAPIKeyAuth = Depends(user_api_key_auth),
):
    """
    Delete an access group.
    

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Check proxy server logs for the underlying exception details.
2. Verify the access group exists and referenced models are valid.

When it happens

Trigger: Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:724 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/757cb3518edf94e2. Report an issue: GitHub.