Add fetch_timeout and cache_fallback search parameters - #197
Merged
Merged
Conversation
Follow-on to the tavily-search max_hours parameter (approved in the same Slack thread). Named params on search()/_search(), sync and async, threaded through to the request body exactly like every other optional parameter -- omitted when unset. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…cache-fallback # Conflicts: # tavily/async_tavily.py # tavily/tavily.py # tests/test_search.py
yashb1708
previously approved these changes
Sep 17, 2026
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
yashb1708
approved these changes
Sep 17, 2026
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
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.
Summary
fetch_timeout(float, seconds) andcache_fallback(bool) tosearch()and the internal_search(), in bothTavilyClientandAsyncTavilyClientNone/unset by default and only sent to the API when explicitly providedmax_hoursparameter (tavily-search):fetch_timeoutbounds the live-fetch timeout for raw-content/freshness-triggered fetches,cache_fallbackcontrols whether a failed/timed-out freshness refetch falls back to the stale cached copy