Loading Profile...
Tweet Limit Exceeded
I haven't signed on with a twitter client for over a day now and my client still says that I've been paused. "Limit exceeded, paused 5 mins." I've tried multiple different clients. This has been happening now for about a week.
I’m sad
36
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Due to volume, only the 15 most recent replies are being displayed
-
Inappropriate?Absolute crap. I have the same problem. I open Twhirl, it runs for a bit, then without doing anything, I get the limit exceeded message. I have Twhirl set at the default settings of 60 req/hour.
Twitter *cough* "support" directed me here instead of trying to resolve the issue.
My account never gets reset. I've reset my password. Numerous times.
Twitter support just doesnt want to address the issue and rather tell me why API limits are reached after I've mentioned numerous times that I havent done anything to come close to the limit.
From this morning...
<hash>
<reset-time-in-seconds type="integer">1228415397</reset-time-in-seconds>
<reset-time type="datetime">2008-12-04T18:29:57+00:00</reset-time>
<remaining-hits type="integer">-10</remaining-hits>
<hourly-limit type="integer">100</hourly-limit>
</hash>
From 15 minutes ago....
<hash>
<reset-time type="datetime">2008-12-04T22:53:44+00:00</reset-time>
<remaining-hits type="integer">-11</remaining-hits>
<hourly-limit type="integer">100</hourly-limit>
<reset-time-in-seconds type="integer">1228431224</reset-time-in-seconds>
</hash>
Incredibly frustrated with all this.
I’m really ticked off.
1 Comment
Add a comment
This solves the problem
-
Hi David. Is there a chance that a third-party service is accessing your Twitter account and therefore eating into your API rate limit?
For example, I use Twittermail to get @replies emailed to me and it checks my Twitter account at regular intervals without any action on my part. I usually don't remember it at all until I get an email from the service.
Other people have signed up for third-party services like TweetLater.com or SocialToo.com to send automated thank-you DMs to people who follow them. That too, eats into the API rate limit since it regularly checks if new people have followed them.
Anyway, one simple way to test this possibility is to temporarily change your Twitter password for a day or two and see if the rate limit problem recurs. If the problem disappears, then there's a good chance that a third-party service was competing with Twhirl for the hourly API limit.
Oh, and the page for logging support tickets with Twitter Support is this one: http://twitter.com/help -
Inappropriate?As I already stated, I'd changed my password.
There are no 3rd party services accessing my account.
I've already logged a support ticket with Twitter. Their script reading responses were a waste of time and didnt resolve anything.2 Comments Add a comment
This solves the problem
-
davidhowell, do I understand correctly -- that the Twitter account in question also has the username "davidhowell"?
If yes, I just checked the account right now and the API request limit currently reads: "0/100 since first request at Wed Dec 10, 2008 07:42:54".
So the API limit appears to be resetting correctly as of now.
Before you turn on Twhirl again, can you perform the rate_limit_status check (using the URL http://twitter.com/account/rate_limit...) just to confirm that you're getting the same figure as I am?
Then, after Twhirl performs its first refresh, can you perform the rate_limit_status check to see how many calls Twhirl consumed in that single refresh?
The rate_limit_status API call doesn't count against the API limit, so you should be able to perform that call even if the rate limit is already exceeded.
We've currently got a bug filed to look into reports of negative API request counts, and I've added your original report (above) to it. If you encounter another negative request number after hitting the limit, it will be good to have any stats that you can provide as additional input. Thanks. -
davidhowell, are you currently accessing your account? After hours of remaining at zero, your API usage is currently going up and at this moment is at "36/100 since first request at Wed Dec 10, 2008 14:30:48"
-
Inappropriate?Yes.
I checked the limit_rate_status limit at 8:31am CST. This was showing...
<hash>
<remaining-hits type="integer">100</remaining-hits>
<reset-time type="datetime">2008-12-10T15:30:48+00:00</reset-time>
<hourly-limit type="integer">100</hourly-limit>
<reset-time-in-seconds type="integer">1228923048</reset-time-in-seconds>
</hash>
I opened Twirl at 8:33am CST and after the first refresh, it showed this...
<hash>
<remaining-hits type="integer">97</remaining-hits>
<hourly-limit type="integer">100</hourly-limit>
<reset-time-in-seconds type="integer">1228923048</reset-time-in-seconds>
<reset-time type="datetime">2008-12-10T15:30:48+00:00</reset-time>
</hash>
Now, at 9:16am CST, the limit_rate_status shows this...
<hash>
<reset-time-in-seconds type="integer">1228923048</reset-time-in-seconds>
<reset-time type="datetime">2008-12-10T15:30:48+00:00</reset-time>
<remaining-hits type="integer">43</remaining-hits>
<hourly-limit type="integer">100</hourly-limit>
</hash>
I havent posted anything nor have I hit the refresh button on Twhirl. The network settings in Twhirl are set at 80 req/hour.
What has happened in the past is that it will eventually hit the limit, I'll close Twhirl wait at least an hour and the reset time wont get reset and the numbers go into the negatives.
I'll post again the results once I get the limit exceeded message.1 Comment Add a comment
This solves the problem
-
davidhowell, can you do a rate-limit check now?
I just checked (since one hour has elapsed from the time you started) and the API rate limit appears to have reset correctly. Can you please confirm for me if you see the same figures?
Twhirl appears to have gone all the way up to 74/100 before the reset. -
Inappropriate?Just checked the rate limit.
<hash>
<reset-time-in-seconds type="integer">1228926650</reset-time-in-seconds>
<reset-time type="datetime">2008-12-10T16:30:50+00:00</reset-time>
<remaining-hits type="integer">49</remaining-hits>
<hourly-limit type="integer">100</hourly-limit>
</hash>
The limit did appear to reset correctly. In the past, this has not always been the case though. I'll continue to check throughout the day.
Thanks for looking into this. I appreciate it.1 Comment Add a comment
This solves the problem
-
Thanks for confirming. I waited for a second hour to pass then checked the rate limit again; it appears to have reset correctly once more.
One possibility that comes to mind -- did you by any chance change your Twitter password to an old, previously-used password when you encountered the rate limit exceeded error?
If yes, it's possible that a third-party app somewhere still has your old password, so when your password was reverted to the old password, the third-party app was able to access your account once more and consume your API limit.
(Fwiw, this has actually happened to another user before, so it's not entirely far-fetched.)
In any case, I'm glad that the issue appears to have been resolved for now. If you encounter the problem again, please don't hesitate to contact Support at http://twitter.com/help. Thanks. -
Inappropriate?There we go. Limit Exceeded and I havent done anything other than have Twhirl open today.
<hash>
<remaining-hits type="integer">-3</remaining-hits>
<hourly-limit type="integer">100</hourly-limit>
<reset-time-in-seconds type="integer">1228953481</reset-time-in-seconds>
<reset-time type="datetime">2008-12-10T23:58:01+00:00</reset-time>
</hash>1 Comment Add a comment
This solves the problem
-
Thanks for posting this. Question -- did you have Twhirl open all day today? Meaning, is it correct to say that things were fine for 9 hours until you got the negative rate limit figure 2 hours ago?
Will escalate. Thanks. -
Inappropriate?At one point, about an hour or so before this happened, I lost my internet connection. I had shut down Twhirl for that time.
Other than that, I had Twhirl open. I havent reopened Twhirl since I received the Limit Exceeded message and only used the Twitter website.
I just check the Rate Limit Status and it gave me the following...
<hash>
<hourly-limit type="integer">100</hourly-limit>
<reset-time-in-seconds type="integer">1228963933</reset-time-in-seconds>
<reset-time type="datetime">2008-12-11T02:52:13+00:00</reset-time>
<remaining-hits type="integer">-4</remaining-hits>
</hash>
It looks like it's not resetting.1 Comment Add a comment
This solves the problem
-
Noted. Thanks for the additional info.
-
Inappropriate?It's still happening.
<hash>
<remaining-hits type="integer">-6</remaining-hits>
<hourly-limit type="integer">100</hourly-limit>
<reset-time type="datetime">2008-12-13T00:03:54+00:00</reset-time>
<reset-time-in-seconds type="integer">1229126634</reset-time-in-seconds>
</hash>
Got the Limit Exceeded message earlier today. Havent used Twhirl since. Just tried opening Twhirl and...well, I'm sure you can guess. -
Inappropriate?Here we are. 4 hours later. Havent used Twhirl and only the Twitter website occasionally since the Limit Exceeded message...
<hash>
<remaining-hits type="integer">-7</remaining-hits>
<reset-time type="datetime">2008-12-13T04:06:43+00:00</reset-time>
<hourly-limit type="integer">100</hourly-limit>
<reset-time-in-seconds type="integer">1229141203</reset-time-in-seconds>
</hash>
Yeah...some function of Twitter is broken. I wonder how many other users are experiencing this problem and just give up on the service rather than pursue it. Or....am I the only one out of all other users that are experiencing this issue?
Regardless, it's infuriating. -
Inappropriate?davidhowell, apologies for the inconvenience.
You're not the only one experiencing this, and we've got a bug ticket filed.
I've now transferred the data that you provided above to another thread in this forum which talks about this problem.
(I believe the original issue from 10 months ago that was the subject of this thread has been solved and we seem to be dealing with a new, different issue now.)
You'll find the other thread (and another user experiencing the same issue) at: http://gsfn.us/t/o4o#reply_704071.
Please click the "I have this problem too" button in the other thread as I will be posting all future updates regarding this issue there.
Thanks and sorry again for the inconvenience. -
Inappropriate?We're currently tracking this issue here: http://gsfn.us/t/o4o#reply_709599
Future updates regarding this will be posted in the other thread. Thanks.
