Chapter 4. Living with the Quotas
One of the daily irritations of Apps Script is being caught by quota limitations that cause scripts to fail. Quotas are imposed on many Apps Script services because they run on shared infrastructure. Runaway processes could have a serious impact on other Apps Script users, and this quota system is intended to protect the Apps Script community as a whole, even though individual users might be occasionally inconvenienced.
Another good reason for quotas is as a signal that an application is no longer suitable for the Apps Script environment, and should be moved to a paid and more scalable environment such as App Engine.
To VBA users, who have free reign over the local PC resources, this can come as somewhat of a culture shock, because these quotas deeply affect the approach to application structure. Although VBA has no direct corollary to this problem, it is important to understand how quotas affect Apps Script development.
The chapter looks at some ways to live with quotas, rate limits, and what Google calls limitations.
The Quotas
Many of the underlying APIs used by Apps Script have their own quotas, but Apps Script often has additional restrictions.
Daily Limits
Some services allow you to perform a maximum number of a particular operation per day; that is, when you exhaust this quota, you can no longer perform that specific operation that day. Table 4-1 lists the daily limits from the Apps Script dashboard at the time of writing.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access