Troubleshoot API errors

This page describes how to troubleshoot errors with the Sheets API.

Note: The Status Dashboard is a good place to start when troubleshooting errors with the Sheets API. It provides real-time information about the status of the Sheets API.

400 Bad Request

This error indicates that the request was malformed. For troubleshooting these requests, see the reference documentation and the support page.

500 Internal Server Error

If you are encountering 500 errors when using the Sheets API, it typically indicates that there is an issue with the API itself. File a bug report on the Sheets API Issue Tracker with the request that caused the error.

503 Service Unavailable

The Sheets API returns a 503 error when the service is unavailable or when the complexity of the request or spreadsheet is high. The following are some suggestions to limit the rate of 503 errors by modifying the API requests and the underlying spreadsheet.

Request

• Use batchUpdate to combine related updates into a single request. Exercise caution when batching large updates as this might trigger a timeout.
• Limit the number of concurrent requests to the API per spreadsheet to 1 request per second.
• For large spreadsheets, retrieve only the necessary spreadsheet values using A1 notation and limit the use of includeGridData.
• Use field masks to limit the amount of data returned by the API.
• Use exponential backoff when retrying requests.

Spreadsheet

• For frequently updated sheets, rotate to a new spreadsheet periodically to reduce accumulation of versions.
• Limit the use of IMPORTRANGE, QUERY, and other complex formulas.
• Consider splitting large spreadsheets into multiple spreadsheets.
• Limit the use of a single spreadsheet as a source for many IMPORTRANGE formulas.
• Limit access to the spreadsheet to only those who need it.