Fix: Responses API now respects global request_timeout #12211
+212
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Modified ProxyBaseLLMRequestProcessing to use litellm.request_timeout when user_request_timeout is None - Added comprehensive tests to verify timeout behavior in responses API - Ensures consistency with other API endpoints that already respect global timeout settings This fixes the issue where responses API was timing out at 30 seconds instead of respecting the configured global request_timeout value.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ishaan-jaff
requested changes
Jul 1, 2025
| @@ -303,6 +301,13 @@ async def common_processing_pre_call_logic( | |||
| self.data["temperature"] = user_temperature | |||
| if user_request_timeout: | |||
| self.data["request_timeout"] = user_request_timeout | |||
| elif ( | |||
There was a problem hiding this comment.
this is the wrong place. It should be on responses/main.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title
Fix: Responses API now respects global request_timeout
Relevant issues
Fixes LIT-272
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/directory, Adding at least 1 test is a hard requirement - see detailsmake test-unitType
🐛 Bug Fix
Changes
This PR fixes an issue where the responses API endpoints were not respecting the global
request_timeoutconfiguration value and were timing out after 30 seconds instead.Problem
request_timeoutinlitellm_settingswas set to a larger valueSolution
ProxyBaseLLMRequestProcessing.base_process_llm_requestto check forlitellm.request_timeoutwhenuser_request_timeoutis NoneTesting
Added comprehensive tests in
tests/proxy_unit_tests/test_responses_api_timeout.py:request_timeoutfrom config is properly propagatedProxyBaseLLMRequestProcessingAll tests pass: