BerriAI/litellm · error · HTTPException

Failed to update Vantage settings: {e}

Error message

Failed to update Vantage settings: {e}

What it means

Catch-all 500 in update_vantage_settings: the read-merge-write flow (loading current settings, merging fields, persisting via _set_vantage_settings) threw an unexpected error such as a database failure. The underlying exception is logged before this generic wrapper is raised.

Source

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

            if request.base_url is not None
            else current_settings.get("base_url", "https://api.vantage.sh")
        )

        await _set_vantage_settings(
            api_key=updated_api_key,
            integration_token=updated_token,
            base_url=updated_base_url,
        )

        verbose_proxy_logger.info("Vantage settings updated successfully")

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

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


async def is_vantage_setup_in_db() -> bool:
    """Check if Vantage is setup in the database."""
    try:
        from litellm.proxy.proxy_server import prisma_client

        if prisma_client is None:
            return False

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

        return vantage_config is not None and vantage_config.param_value is not None

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Check proxy logs for the underlying error, verify the payload fields, and retry the update.

When it happens

Trigger: Thrown at litellm/proxy/spend_tracking/vantage_endpoints.py:240 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/86c4ddbd3b0d79cc. Report an issue: GitHub.