BerriAI/litellm · error · HTTPException

Failed to perform Vantage dry run export: {e}

Error message

Failed to perform Vantage dry run export: {e}

What it means

Catch-all 500 wrapping the Vantage dry-run export: querying spend data, normalizing it, or building the sample/summary threw an unexpected exception. Because it is dry-run, no data was sent to Vantage; the original error is logged with traceback.

Source

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

            "usage_data": usage_sample,
            "normalized_data": normalized_sample,
            "summary": summary,
        }

        verbose_proxy_logger.info("Vantage dry run export completed successfully")

        return VantageExportResponse(
            message="Vantage dry run export completed successfully.",
            status="success",
            dry_run_data=dry_run_result,
            summary=summary,
        )

    except HTTPException:
        raise
    except Exception as e:
        verbose_proxy_logger.error("Error performing Vantage dry run export: %s", e)
        raise HTTPException(
            status_code=500,
            detail={"error": f"Failed to perform Vantage dry run export: {e}"},
        )


@router.post(
    "/vantage/export",
    tags=["Vantage"],
    dependencies=[Depends(user_api_key_auth)],
    response_model=VantageExportResponse,
)
async def vantage_export(
    request: VantageExportRequest,
    user_api_key_dict: UserAPIKeyAuth = Depends(user_api_key_auth),
):
    """
    Perform an actual export using the Vantage logger.

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Verify Vantage settings and credentials are configured, then check logs for the underlying export error.

When it happens

Trigger: Thrown at litellm/proxy/spend_tracking/vantage_endpoints.py:420 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/4fcc10ecbf37452b. Report an issue: GitHub.