Anonymous - 2013-08-08

Originally posted by: StalkR

Unfortunately "API rate limit exceeded" is an expected error: Twitter doesn't provide a single API "tell me the new tweets for these users". So we have to burn API quota by making 1 request / user to check for new tweets, and this quickly reaches the "API rate limit exceeded" error.

But it's all good: the archiver sleeps until it has more quota, just let it finish and all users tweets will be archived.
If you cancel before the end, it indeed goes back at the beginning as it doesn't know resume.

So in my opinion it's working as intended. However if the archiver doesn't go to sleep to wait for more quota after an "API rate limit exceeded" (i.e. the error breaks the script), then yes that's a bug. Is it what happens?