Hi all,
Around 3am this morning (UK time) we started receiving lots of ‘Rate Limit Exceeded’ errors for a number of my client’s installations. Interestingly this didn’t happen across all installations.
The job that returned this error calls statuses/show/:id a maximum of 150 times per authenticated user account. This happens every couple of hours.
The rate limit table here:
https://dev.twitter.com/docs/rate-limiting/1.1/limits
Suggests a maximum of 180 per 15 minute window.
What appears to be happening is that it processes up to 15 for one account, and the 16th request for that account, plus all subsequent requests for any account also fail.
It’s been working for over a year with no problems, and there’s been no code changes to this for at least a couple of months so intrigued as to why it’s started happening.
Does anyone have any ideas?
Many thanks,
Kev