Why am I suddenly getting “Response status code does not indicate success: 429 (Too Many Requests).” errors when I try to query my table? I have been using this table for 6+ months with no issues until now. Did something change? This is very concerning, as my app highly depends on this table. Please help.
Please see
here: Zapier and Error 429 and
here: Introduction of Team API Limits at SeaTable Cloud and also
here: Important Changes to the SeaTable Cloud API in Version 5.3
Why do you even bother to offer a free plan if you’re going impose unreasonable limits? You just wasted a month of my time integrating your database into my app. I will be looking for an alternative & will not recommend your service to other developers.
Hi @nbrege,
Sorry but I have to say that your answer sounds a bit rude to me:
- you say that you use the table for 6+ months, the introduction of these limits have been announced a long time ago (February 2024 and again May 2025). Besides, I can understand you’re upset, but I don’t think anybody wasted a month of your time on purpose (to some extent it was probably also your responsibility to ensure that the system’s operating conditions were acceptable for your application, don’t you think?)
- these limits don’t seem unreasonable, at least to me
Did you consult this help article to see how you could eventually lower the number of your API calls?
Bests,
Benjamin
2 Likes
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
