Script error Request failed for https

Home Forums TAGSExplorer Questions/Issues Script error Request failed for https

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1144
    leninmaury
    Participant

    Hello,
    What does it mean this error type?
    Request failed for https://api.twitter.com/1.1/search/tweets.json?q=Tibisay%20AND%20Lucena&count=100&result_type=recent&include_entities=1&since=2018-02-01&until=2018-02-07&tweet_mode=extended&max_id=959895918014234625 returned code 429. Truncated server response: {“errors”:[{“message”:”Rate limit exceeded”,”code”:88}]} (use muteHttpExceptions option to examine full response)

    #1145
    mhawksey
    Keymaster

    Hi – Twitter limits the amount of data you can collect per 15 minute window. The limit is applied to your account rather than per sheet so if you have lots of TAGS sheets running you can hit rate limits. The limit is quite generous and you should be able to get a max of 180k tweets per 15 mins

    #1240
    Quirin
    Participant

    Sorry, but one more question about rate limiting.

    First of all: is the total limit 18,000 (what I thought) or 180,000 as implied above?

    I’m currently using about 30 sheets in parallel, and I’m trying to figure out to set up the maximum number of tweets, so that I won’t exceed the rate limit for any of the queries. Would it make sense to set the limit for each individual sheet to 18,000 / 30 so that the maximum cannot be reached? Ideally, I’d want to set it up in a way so that I get no ceiling effects at all.

    And if I want to even increase the number of parallel queries I would probably have to switch to a different setup involving the Streaming API, right?

    Best,
    Quirin

    #1244
    mhawksey
    Keymaster

    The calculation is 180 data calls per 15mins and each call can get a maximum of 100 tweets. As one call might not return a maximum 100 tweets tricky to load balance.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.