BerriAI/litellm · error · HTTPException

Vantage settings not found

Error message

Vantage settings not found

What it means

DELETE /vantage/settings found prisma_client connected but no VANTAGE_SETTINGS_PARAM_NAME row in LiteLLM_Config, so there is nothing to delete. Usually means settings were already deleted or never initialized via /vantage/init.

Source

Thrown at litellm/proxy/spend_tracking/vantage_endpoints.py:533

            status_code=403,
            detail={"error": CommonProxyErrors.not_allowed_access.value},
        )

    try:
        from litellm.proxy.proxy_server import prisma_client

        if prisma_client is None:
            raise HTTPException(
                status_code=500,
                detail={"error": CommonProxyErrors.db_not_connected_error.value},
            )

        vantage_config: Final = await ConfigRepository(prisma_client).table.find_first(
            where={"param_name": VANTAGE_SETTINGS_PARAM_NAME}
        )

        if vantage_config is None:
            raise HTTPException(
                status_code=404,
                detail={"error": "Vantage settings not found"},
            )

        await ConfigRepository(prisma_client).table.delete(where={"param_name": VANTAGE_SETTINGS_PARAM_NAME})

        # Deregister in-memory VantageLogger so the scheduler stops firing
        from litellm.integrations.vantage.vantage_logger import VantageLogger

        litellm.logging_callback_manager.remove_callbacks_by_type(litellm.callbacks, VantageLogger)

        verbose_proxy_logger.info("Vantage settings deleted successfully")

        return VantageInitResponse(message="Vantage settings deleted successfully", status="success")

    except HTTPException:
        raise
    except Exception as e:

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Initialize Vantage settings via /vantage/init before calling this endpoint.

When it happens

Trigger: Thrown at litellm/proxy/spend_tracking/vantage_endpoints.py:533 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/29b581c222696535. Report an issue: GitHub.