HTTP 429 indicates that a Sheets API request exceeded an applicable rate quota. Use bounded retries with backoff, while treating ambiguous writes separately from a clear rejection.
Inspect the quota and request pattern
Check the response details and the project’s actual quota usage. Sheets has per-minute project and per-user-per-project limits; the smaller applicable allowance can constrain the client.
Look for several workers or repeated polling sharing the same quota. More concurrent retries can worsen the problem even when each worker appears modest in isolation.
Apply bounded exponential backoff
Google recommends truncated exponential backoff with random jitter. Increase delays up to a configured maximum and stop after an appropriate attempt or elapsed-time limit.
Batch suitable operations and reduce unnecessary reads. Keep payloads manageable and do not assume a quota adjustment is automatically granted. Read the current limits before planning a sustained workload.
Reconcile uncertain write outcomes
A definite 429 rejection differs from a network timeout after a write might have reached the service. For an append or other non-idempotent operation, inspect the destination using stable keys before blindly resending.
Google documents atomic application within a Sheets update request, but a multi-request business workflow is not automatically one transaction. Persist completed-unit evidence and retry only the unresolved portion. Test interruption and duplicate prevention on a small authorized copy. Report exhausted retries as incomplete work, with counts and safe error details, rather than continuing indefinitely or claiming success because the client eventually stopped receiving errors. Keep read retries distinguishable from write retries in diagnostics.
References
- Usage limits | Google Sheets | Google for Developers
- Troubleshoot API errors | Google Sheets | Google for Developers
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.