-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Zero results found for the search query." when running SearchGraph #897
Comments
Hey there, @KaaustaaubShankar! I'm here to help you with any bugs, questions, or contributions. Let's work together to solve the issue you're facing. The "Zero results found for the search query" error occurs because the To troubleshoot this issue, consider the following steps:
By addressing these areas, you should be able to resolve the issue and obtain the expected search results. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
I am also experiencing the same issue, using the google colab scrapegraphai demo. A few days ago SearchGraph worked correctly, now I am getting the same error. |
Yea, I just started getting this on every request today. Yesterday I wasn't having the problem. Looks like the google search package is having problems. Edit: Here is the issue on the |
I thought it was only me lmao I was like tryna adjust me code constantly until I realised that it happened to everyone xD |
Adding "search_engine": "duckduckgo" to the graph config helps (if you don't insist using google) |
Describe the bug
When I attempt to use SearchGraph through run(), I am given "Zero results found for the search query"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The answer of the prompt in json form. In this case it should have been "European Countries" with a list of the companies as the value.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: