BerriAI/litellm · error · HTTPException

Failed to delete polling response

Error message

Failed to delete polling response

What it means

Polling deletion failure: the state existed and access was verified, but ResponsePollingHandler.delete_polling returned failure — the Redis delete operation did not succeed (connectivity or key issues); surfaced as an error after the existence checks passed.

Source

Thrown at litellm/proxy/response_api_endpoints/endpoints.py:836

        # Handle polling response deletion
        if not redis_usage_cache:
            raise HTTPException(status_code=500, detail="Redis cache not configured.")

        polling_handler: Final = ResponsePollingHandler(redis_cache=redis_usage_cache)

        # Get state to verify access
        state: Final = await polling_handler.get_state(response_id)

        if not state:
            raise HTTPException(status_code=404, detail=f"Polling response {response_id} not found")

        # Delete from cache
        success: Final = await polling_handler.delete_polling(response_id)

        if success:
            return DeleteResponseResult(id=response_id, object="response", deleted=True)
        else:
            raise HTTPException(status_code=500, detail="Failed to delete polling response")

    # Normal provider response flow
    data: Final = await _read_request_body(request=request)
    data["response_id"] = response_id
    processor: Final = ProxyBaseLLMRequestProcessing(data=data)
    try:
        return await processor.base_process_llm_request(
            request=request,
            fastapi_response=fastapi_response,
            user_api_key_dict=user_api_key_dict,
            route_type="adelete_responses",
            proxy_logging_obj=proxy_logging_obj,
            llm_router=llm_router,
            general_settings=general_settings,
            proxy_config=proxy_config,
            select_data_generator=select_data_generator,
            model=None,
            user_model=user_model,

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Check Redis connectivity and logs; retry the delete once the cache is reachable.

When it happens

Trigger: Thrown at litellm/proxy/response_api_endpoints/endpoints.py:836 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/855b42c071dd3709. Report an issue: GitHub.