dsgerbc

The simple reason for the error is that the pytrends code does not bother with try/except constructs at all. It only throws a google error is the results.status!=200. Throw some...

Do you have try/except in your pytrends interactions? If yes and those aren't catching this timeout try: 1) Zeroing out pytrends retries/timeout options. I think there's something going on with...

It's in the pull request #411 linked above. https://github.com/GeneralMills/pytrends/pull/411/commits/2ae4ccc67547768cf9b9160f5126369b190264ab