BerriAI/litellm · error · HTTPException

Failed to delete Vantage settings: {e}

Error message

Failed to delete Vantage settings: {e}

What it means

Catch-all 500 in delete_vantage_settings: deleting the config row or deregistering the in-memory VantageLogger callback threw an unexpected error. The config-row delete may have succeeded before the failure, so state can be partially torn down; the original exception is logged.

Source

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

                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:
        verbose_proxy_logger.error("Error deleting Vantage settings: %s", e)
        raise HTTPException(
            status_code=500,
            detail={"error": f"Failed to delete Vantage settings: {e}"},
        )

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Check proxy logs for the underlying error and confirm the settings exist before deleting.

When it happens

Trigger: Thrown at litellm/proxy/spend_tracking/vantage_endpoints.py:553 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/2b5b4182a06ea2ea. Report an issue: GitHub.