BerriAI/litellm · error · HTTPException

Failed to delete access group: {e}

Error message

Failed to delete access group: {e}

What it means

Catch-all around the access-group deletion transaction: unexpected exceptions while stripping the group from deployments or deleting it are logged and re-raised as this 500; HTTPExceptions (validation/404) pass through.

Source

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

            written_models=removed_pairs,
            access_group=access_group,
        )

        verbose_proxy_logger.info(
            "Successfully deleted access group '%s' from %s deployments", access_group, models_updated
        )

        return DeleteModelGroupResponse(
            access_group=access_group,
            models_updated=models_updated,
            message=f"Access group '{access_group}' deleted successfully",
        )

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

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Check proxy server logs for the underlying exception details.
2. Verify the access group exists before deleting.

When it happens

Trigger: Thrown at litellm/proxy/management_endpoints/model_access_group_management_endpoints.py:825 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/3451c5563c1e350a. Report an issue: GitHub.