#1

My bot has been successfully searching Twitter once a minute via the api for well over a year, when suddenly as of Oct. 31st the api is 99.999% returning 130 and 131 errors. As of this moment it’s about 8,700 errors since they started.
Anyone else having this issue?
Is this forum the best place to get input from other devs?

TIA

38%20PM
38%20PM1056×384 50.4 KB

#2

Hi,

Thanks for reaching out here. Error code 130 is an over capacity error. This corresponds with HTTP 503. Twitter is temporarily over capacity. Error 131 is an Internal error and corresponds with HTTP 500 meaning an unknown internal error occurred.

Can you let us know a bit more about what’s going on here? What endpoint are you hitting? Do you have a code snippet you can send over.

Thanks!

Jessica

#3

Here’s the search.
T.get(‘search/tweets’, { q: ‘trump min_retweets:1000’, count: 100 } …

I have noticed that if I change to min_retweets:200 or smaller then the api throws either less errors or none at all, which seems super odd to me, but it is what it is.

Thank you so much for replying, I’ll take any help I can get!

#5

Jessica, is there a timeline for fixing the errors?
It is wreaking havok with my bot and making me sad ;(

#6

You mentioned that you see fewer errors when you’re using a smaller query / smaller number of results, since HTTP error 500 and 503 are intentionally temporary, are you able to experiment with alternative smaller queries? There’s nothing obvious that would attach this to a specific individual app.

#7

I did change the min_retweets to 100 and now the api returns data maybe 10% of the time, the rest are still errors.
Also, if I go to a regular twitter.com page and put ‘obama min_retweets:100’ into the search box I get the same errors, so you should be able to see the same issue I am seeing by trying this.
The unfortunate part for me is that I was measuring the approximate time tweets took to reach 1,000 retweets, and while it wasn’t perfect I was getting pretty reliable data for more than a year. Now with the search failing most of the time if the issue doesn’t get resolved I’ll likely have to end the project.
Here’s a link to the companion website for the bot I created: https://viraltrumptweets.com/weekly
Have a look!

#8

So, is min_retweets not a thing anymore? I notice that in Tweetdeck the Engagement feature works just fine and it seems to be the exact same function.

#9

It’s working! Someone fixed it! Back in business!
Thanks Twitter.

#10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.