Request failed: 429 - {"title":"Too Many Requests","detail":"Too Many Requests","type":"about:blank","status":429}

[Br4ndonP0nce]

It was originally working just fine my loops are set to 900 secs, tried to bring it back up and the twitter connection shows as not configured, i tried to reconnect and it returns that error, any idea on what could it be?

[ef95023]

hi friend

first thing to do would be to check that json syntax and bracketing has not somehow accidentally been broken in your agent json

after that, try resetting your twitter environment variables

change them back to empty strings in your .env file like so

TWITTER_USERNAME='' TWITTER_USER_ID='' TWITTER_CONSUMER_KEY='' TWITTER_CONSUMER_SECRET='' TWITTER_ACCESS_TOKEN='' TWITTER_ACCESS_TOKEN_SECRET=''

then configure the connection again via the configure-connection twitter command

hopefully it resolves your issue, let me know how it goes

[Br4ndonP0nce]

It turns out that the twitter api is trash so 1 request finished my requests for the day ahaha, thank you! Btw is there any way to make the requests more efficient or should i just consider upgrading my api?

[MaxHuber888]

Just one request should not hit rate limits, even for the free tier (here are the rate limits for each endpoint / each tier https://developer.x.com/en/docs/x-api/rate-limits). Can you give some more information about the action you were trying to perform and whether you had used the api previously on the same day?

[Br4ndonP0nce]

Hey @MaxHuber888 ! I started an agent loop to read and post my openai api had only one request which was the twitter post ,after the twitter connection just couldnt be used anymore, i revoked the twitter api key, tried with another twitter account and only then it worked, i tried to reconnect the first account and it returns that error > Just one request should not hit rate limits, even for the free tier (here are the rate limits for each endpoint / each tier https://developer.x.com/en/docs/x-api/rate-limits). Can you give some more information about the action you were trying to perform and whether you had used the api previously on the same day?

[MaxHuber888]

Even on the free tier, you should be able to make 17 requests to the endpoint for posting tweets per 24 hours. The only three things I can think of are:

• if you were retrieving a ridiculous amount of tweets from the timeline (is this a value you changed in your config at all?)

• if your API key is "read only", for posting tweets you need to allow "read and write" permissions in the dev dashboard

• it may be an issue on Twitter's end, when I look up your error code I see a lot of people complaining about being rate limited without actually having used up their requests for the day.

If it is working with another account now I am guessing it is probably one of the latter two. Thank you for bringing our attention to this we will be looking into this.

[Br4ndonP0nce]

Even on the free tier, you should be able to make 17 requests to the endpoint for posting tweets per 24 hours. The only three things I can think of are:

• if you were retrieving a ridiculous amount of tweets from the timeline (is this a value you changed in your config at all?)
• if your API key is "read only", for posting tweets you need to allow "read and write" permissions in the dev dashboard
• it may be an issue on Twitter's end, when I look up your error code I see a lot of people complaining about being rate limited without actually having used up their requests for the day.

If it is working with another account now I am guessing it is probably one of the latter two. Thank you for bringing our attention to this we will be looking into this.

Hey @MaxHuber888 thanks again for taking the time to respond! this is the twitter settings on the agent config file i used the default example settings for this, the twitter api is set for read and write as well