For teams that are executing a high volume of google sheets deliveries with high frequency, you may be affected by rate limits imposed by Google Sheet’s API. If the frequency of deliveries starts to become shorter than the time in the queue, this is obviously not desirable.
The Google Sheets API imposes coexisting usage limits against the project that owns the Google Sheet, and for the purposes of optimizing, most scenarios may face rate limits with:
-
A per project limit of 300 write requests per minute
-
A per user per project limit of 60 write requests per minute
Our main recommendation to maintain throughput here is to spread the deliveries across multiple unique Google user accounts if you have not already - this should increase throughput ~5x compared to having them all associated with the same user.
Ultimately our interaction Google Sheets API is proportional to how many concurrent schedules are executing and how many rows some execution needs to deliver to a target sheet (we make 1 write request for every ~1000 rows of data). This should be kept in mind as scaling, but for most organizations will not inhibit their use cases.
As you start to add more schedules to google sheets, it is suggested that you monitor the delivery times to confirm the queue is not getting backed up or causing job failures.
Additionally, you should be able to monitor your project’s current usage at https://console.cloud.google.com/apis/api/sheets.googleapis.com/quotas for close visibility on where you may be hitting limits