BerriAI/litellm · error · HTTPException
Failed to perform CloudZero dry run export: {e}
Error message
Failed to perform CloudZero dry run export: {e} What it means
Error "Failed to perform CloudZero dry run export: {e}" thrown in BerriAI/litellm.
Source
Thrown at litellm/proxy/spend_tracking/cloudzero_endpoints.py:427
# Import and initialize CloudZero logger with credentials
from litellm.integrations.cloudzero.cloudzero import CloudZeroLogger
# Initialize logger with credentials directly
logger: Final = CloudZeroLogger()
dry_run_result: Final = await logger.dry_run_export_usage_data(limit=request.limit)
verbose_proxy_logger.info("CloudZero dry run export completed successfully")
return CloudZeroExportResponse(
message="CloudZero dry run export completed successfully.",
status="success",
dry_run_data=dry_run_result,
summary=dry_run_result.get("summary") if dry_run_result else None,
)
except Exception as e:
verbose_proxy_logger.error("Error performing CloudZero dry run export: %s", e)
raise HTTPException(
status_code=500,
detail={"error": f"Failed to perform CloudZero dry run export: {e}"},
)
@router.post(
"/cloudzero/export",
tags=["CloudZero"],
dependencies=[Depends(user_api_key_auth)],
response_model=CloudZeroExportResponse,
)
async def cloudzero_export(
request: CloudZeroExportRequest,
user_api_key_dict: UserAPIKeyAuth = Depends(user_api_key_auth),
):
"""
Perform an actual export using the CloudZero logger.
View on GitHub (pinned to 77b7c6c40c)
Solutions
- Check the error detail; verify CloudZero credentials and spend data availability, then retry the dry run.
When it happens
Trigger: Thrown at litellm/proxy/spend_tracking/cloudzero_endpoints.py:427 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/74a27718db410535.
Report an issue: GitHub.