You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I tried running a deep research with a lot of context describing exactly what I want to search for and how to format it as well as some background information (similar to the kind of input I would give to deep research on chatgpt); but I get multiple errors from tavily saying "Error: 400 Client Error: Bad Request for url: https://api.tavily.com/search. Failed fetching sources. Resulting in empty response.". I printed the full message of the exception and it's because "'{"detail":{"error":"Query is too long. Max query length is 400 characters."}}'".
To Reproduce
Steps to reproduce the behavior:
Set search engine to tavily
Run deep research (probably also other kinds of research) with a long prompt (seemingly >400 characters).
Observe
Expected behavior
I suppose in case of long queries; first there should be a "planning step" or "query rewriting" step; and only after it should proceed to do the actual search?
The text was updated successfully, but these errors were encountered:
Describe the bug
I tried running a deep research with a lot of context describing exactly what I want to search for and how to format it as well as some background information (similar to the kind of input I would give to deep research on chatgpt); but I get multiple errors from tavily saying "Error: 400 Client Error: Bad Request for url: https://api.tavily.com/search. Failed fetching sources. Resulting in empty response.". I printed the full message of the exception and it's because "'{"detail":{"error":"Query is too long. Max query length is 400 characters."}}'".
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I suppose in case of long queries; first there should be a "planning step" or "query rewriting" step; and only after it should proceed to do the actual search?
The text was updated successfully, but these errors were encountered: