HELP: Issues with rate limiting after only a few queries

[escooley]

I am working on a project where I need to gather tweets. In using the TwitterSearch Order object (with my keys and secrets) after only a few queries I get rate limited. I am watching the “x-rate-limit-remaining” value as I am querying…the value below (162) was what I had left and then I was limited.

Please help…don’t want to fail my project and need the full 180 per time interval

Thank you in advance
##############
current remaining queries is: 162
Error 429: ('Too Many Requests: Request cannot be served ', "due to the application’s rate limit having ", ‘been exhausted for the resource’)

[Twitaculous]

Not sure if it’s related, but I seem to be getting this today:
"#88 - Rate limit exceeded"

[escooley]

Still happening…looks like I am being limited to 15 every 15 minutes vs the hundred and something. Not sure why would be nice to know though.

[mattgwilliam]

Any word in this. I am having the same issue. Rather weird.

[andypiper]

On which endpoint? Are you using application-only auth, or user auth?