503 Error with search/all
See original GitHub issueI noticed when searching with --archive that I occasionally am getting this in the log:
2021-04-29 10:14:07,737 WARNING 503 from Twitter API, sleeping 60
I think this is related?
https://twittercommunity.com/t/perpetual-503-v2-full-archive-search-default-vs-all-fields/151441
Hopefully it’s a bug that will be fixed on Twitter’s end. But if not we may need a way to dial down the max_results.
Issue Analytics
- State:
- Created 2 years ago
- Comments:18 (10 by maintainers)
Top Results From Across the Web
Error with Google search in Python: 503 Service Unavailable
I think it´s related with query itself because if I do the same with the query: "site:facebook.com" for example, it works. The problem...
Read more >Full-archive search endpoint only returns error code 503
The code looks almost exactly the same as the sample code. The URL I'm calling is: https://api.twitter.com/2/tweets/search/all . My params are ...
Read more >What is HTTP error 503 and how do you fix it? - IT PRO
An HTTP error 503 is found when your browser encounters a website that is unable to establish a connection with its server. Many...
Read more >HTTP Error 503. The service is unavailable (4216852)
Error showing when accessing Archive Manager site: HTTP Error 503. The service is unavailable.
Read more >Service Unavailable: HTTP Error 503. The ... - SharePoint Diary
Service Unavailable: HTTP Error 503. The service is unavailable error normally occurs whenever the password for the application pool identity account is ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@edsu in this particular search it was 5273637 tweets in a two year time period.
@edsu it worked. Thank you for your interest! I had to wait quite a while, but in the end I got what I wanted. So probably --max-results 100 increases the probability that one gets what he wants, but owing to Twitter this probability is only close to 1 and depends on pure luck. One should not get discouraged after initial failure, only try for a couple of days.