#1

I am getting the “rate limit exceeded: sleeping 400-800 secs” for 10-15 consecutive messages while before each it collects only 95-100 tweets instead thousands of tweets which it used to collect between each two rate limit sleeps!

Is it a bug or am I actually exceeding some limitation?

btw: is there way within twarc (instead of using my dashboard in developer page) to find out whether/how much I have used my monthly twitter cap?

Thanks in advance.

#2

No, because twitter doesn’t provide an API for this anywhere unfortunately 0 it’s only in your dashboard.

What exact twarc command are you running? Do you have the full error from twarc.log ?

1 Like
#3

thanks a lot for your response!

I am running full history search. I was running on a cloud platform and before seeing your reply I stopped the code and started over, so unfortunately i don’t have the log but now it seems to be working again.
I remember a few weeks ago similar thing happened when i extracted tweets for almost 24 hours, maybe that has something to do with it.

1 Like
#4

Sometimes it’s a case of using the same bearer token in multiple scripts running at the same time, either with trying to run different queries while another crawl is happening, or accidentally running 2 instances or using the same bearer token in CI or something like that. Or sometimes the error is due to your system clock being out of sync but that should not really happen.

1 Like