BerriAI/litellm · error · HTTPException
Failed to perform Vantage export: {e}
Error message
Failed to perform Vantage export: {e} What it means
Catch-all 500 wrapping the real Vantage export: fetching usage rows for the requested window or pushing them to the Vantage API failed unexpectedly. Original exception is logged; partial state on the Vantage side is possible if the failure happened mid-upload.
Source
Thrown at litellm/proxy/spend_tracking/vantage_endpoints.py:493
limit=request.limit,
start_time_utc=request.start_time_utc,
end_time_utc=request.end_time_utc,
)
verbose_proxy_logger.info("Vantage export completed successfully")
return VantageExportResponse(
message="Vantage export completed successfully",
status="success",
dry_run_data=None,
summary=None,
)
except HTTPException:
raise
except Exception as e:
verbose_proxy_logger.error("Error performing Vantage export: %s", e)
raise HTTPException(
status_code=500,
detail={"error": f"Failed to perform Vantage export: {e}"},
)
@router.delete(
"/vantage/delete",
tags=["Vantage"],
dependencies=[Depends(user_api_key_auth)],
response_model=VantageInitResponse,
)
async def delete_vantage_settings(
user_api_key_dict: UserAPIKeyAuth = Depends(user_api_key_auth),
):
"""
Delete Vantage settings from the database.
Only admin users can delete Vantage settings.View on GitHub (pinned to 77b7c6c40c)
Solutions
- Verify Vantage settings and credentials, run the dry-run export first, and check logs for the underlying error.
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at litellm/proxy/spend_tracking/vantage_endpoints.py:493 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/056bb7506d87e7ef.
Report an issue: GitHub.