Trying to scrape Twitter for a query but this keeps happening. Have tried changing the parameters (increasing retries, reducing rows returned) but this keeps happening.
ERROR Twitter Search 0:2 Execute failed: connect timed out
Hi @TEQ23 -
Was your workflow running OK before, then suddenly stopped working? We’ve seen this happen before when Twitter makes tweaks on their end that temporarily disrupt query abilities. Usually things return to normal after a few hours in that case.
If this continues, could you send a minimal example workflow or associated error log so we can investigate further?
I am having this problem as well. Has any other possible explanation come to light regarding this error?
The Connector is green, so there shouldn’t be any issues there but the other nodes (search and users) keeps giving me a “Execute failed: connect timed out” error.