Rate Limit 429 triggering without due reason

Hi there, is anyone else having issues today with the API Servers? 429 Error Responses to API calls? Every minute it resets and it appears I’m permitted to send one API request before it blocks again! 'I’ve logged a ticket but wondered if it’s just me or a more widespread issue.

Unfortunately my account hasn’t been enabled with API Logs yet so I’m not able to look at API history from Tadabase.

Graham.

Yes, all of my API calls are currently failing, massive issue. I have submitted a ticket, I hope this is reviewed quickly!

1 Like

Hey Graham, have you had any resolution yet? I received a response to my ticket that everything seemed to be working fine, so I submitted information regarding the errors being received. It looks like we are currently allowed 0 (zero) requests per minute. Definitely something wrong.

yeah I’m still getting the issue, I’ve also logged a call.

I am also getting same issue

1 Like

Hi all, we are investigating this and will update as soon as possible.

1 Like

thanks @Adi if you need any more info just let us know .

1 Like

Our permitted api requests per minute are zero, see api result via test on zapier:

Current Code

200

per_minute_limit

Per Minute Limit Allowed

0

Per Minute Limit Remaining

-1

Per Minute Limit Resets In Seconds

60

Per Minute Limit Reset Timestamp

1764015823

per_day_limit

Per Day Limit Allowed

50000

Per Day Limit Remaining

47555

Per Day Limit Resets In Seconds

22003

Per Day Limit Reset Timestamp

1764037766

1 Like

Yeah I think that’s the same situation for all of us that are dealing with the issue. Same thing where it says 0 for the per minute limit. And it only shows the daily limit if it is a successful request which only happens when it says you’re on second 0 of a new per minute cycle.

And it still shows the remaining per minute as -1 like it does for you there as well.

hi @Adi is there any more info you need, it’s super simple to reproduce the error if you need more info. Is this likely to be reesolved by the morning?

thats’ exactly the same results I shared with them too lets hope this is resolved soon. :folded_hands:

1 Like

Very much an issue on our end and we are working to see what’s going on. Looks like some keys stuck in our caching system. Will have an update again shortly.

2 Likes

Thank you for the update @moe, appreciate it!

Yep thanks for the fix - my system looks like its working okay now thank you.

Yes response API is also replying correctly now with correct API limits.

1 Like

My sincere aplogies about this.

We’re working on an update that purged our cache with the subscription limits and replaced it with incorrect values. We purged our redis cache and this is now cleared and resolved.

4 Likes

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.