I’m experiencing intermittent 429 errors when calling the AppSheet REST API from Google Apps Script, and I wanted to check if anyone else is seeing the same thing recently.
Setup: AppSheet Bot → triggers Apps Script (via “Call a script” task) → Apps Script calls AppSheet API to edit rows in a table.
The problem: Since last week, some API calls return a bare HTML 429 response (not JSON):
<!doctype html><meta charset="utf-8">...429 Too Many Requests
Key observations:
Call frequency is very low: ~3 requests per minute, sequential, no concurrency issues
Other API calls succeed normally around the same time
Nothing changed on our side
Retries with 60s+ backoff sometimes succeed, sometimes don’t
This worked perfectly fine until last week
Interestingly, failed requests show no entry in AppSheet’s Audit Log, and the error response is a bare HTML page rather than AppSheet’s typical JSON error format. This leads us to believe the request may be getting blocked before reaching AppSheet, but we can’t confirm this with certainty. Has anyone seen this pattern before or have any insight into what could cause it?
Questions:
Is anyone else experiencing this recently?
Has anything changed on AppSheet’s infrastructure side in the last week?
Is there any known rate limit that could explain this behavior at such low call frequency?
Thanks Steve! I hope it’s related — at least that thread mentions a revert is already in place. I’ll be monitoring throughout the day to see if the errors clear up.
I have been having the exact same issues as @Juan_Matias on a customer App where I need to use the API. I have been updating the scripts to add exponential backoff but its still failing with a simple 429 a lot.
the errors are still occurring on our end. The revert mentioned in that thread doesn’t seem to have resolved it for us. Still getting the same HTML 429
I received a response from support, and they informed me that they are currently working on the issue. They also identified that the 429 error is not related to AppSheet, but to Apps Script.
Since I use the AppSheet database and integrate all my data into BigQuery, I created a Python script to perform the same process. It successfully handled the integration without any issues, processing over 1,000 requests. The 429 error does not occur when running the process in another language instead of Apps Script.
At least for now, this serves as a temporary workaround until the issue is resolved.
I just want to say that I’m in exactly the same situation (Apps Script calling AppSheet APIs).
I have a workaround that’s not 100% reliable (= repeated backoffs).
This will soon become a critical situation. I don’t have another server available to run a Node or Python script.
Hi Shourya. Is this currently prioritized on your side, and is the AppSheet support team actively following the investigation? Also, since you mentioned it appears to be an Apps Script issue rather than AppSheet, is there a better official channel or tracker we should use for updates on the Apps Script side?