Google Apps Script stops any single execution after six minutes, on consumer and Workspace accounts alike. Daily quotas depend on the account: triggers may run for 90 minutes a day on a consumer account and six hours on Workspace. No setting or support request raises them, which is why heavy Autocrat and Sheets automations eventually fail.
Questions this guide answers
What is the Google Apps Script execution time limit in 2026?
Both consumer (free) and Google Workspace accounts are capped at 6 minutes per execution in 2026: the 30-minute Workspace limit cited by older guides no longer applies. Scripts that exceed the limit are hard-stopped mid-run: no graceful shutdown, no warning, just termination.
What is the daily runtime limit for Google Apps Script in 2026?
Google's official quota for triggers total runtime is 90 minutes per day on consumer accounts and 6 hours per day on Workspace accounts. This applies to trigger-driven executions; manual runs are not counted. The quota resets 24 hours after the first request.
What is the Google Apps Script UrlFetch daily limit?
Consumer accounts can make 20,000 UrlFetch calls per day. Google Workspace accounts get 100,000 per day. If your automation calls external APIs on every order, this limit can be exhausted faster than expected on high-volume days.
Have Google Apps Script quotas changed for 2026?
The core limits, 6-minute execution (both consumer and Workspace) and 90-minute daily trigger runtime on consumer accounts, have remained consistent into 2026. Google does not announce quota changes prominently. If you are seeing new failures, it is more likely that your volume has grown into the limits rather than that Google has tightened them.
Can Google Apps Script quotas be increased?
Not by request or configuration. Google publishes one set of figures for consumer accounts and a higher set for Google Workspace accounts, so moving to Workspace raises the daily quotas, such as trigger runtime and URL Fetch calls. The six-minute limit per execution is the same on both. To work beyond it, move the work outside Apps Script, into Make.com or a dedicated API layer.
Why does my script work in the morning but fail in the afternoon?
This is the clearest sign of a daily quota problem. Trigger-driven automations are exhausting the 90-minute daily trigger runtime (consumer) in the first half of the day, leaving nothing for afternoon processing. The quota resets 24 hours after the first request, which is why timing shifts day to day.
Why does the same script work one day and fail the next?
Variable load. A day with higher order volume or more form submissions hits limits that a quieter day never reached. The script did not change: the pressure on its quota allowance did.
Is Apps Script still useful for automation in 2026?
Yes: as a lightweight trigger and orchestration layer for simple spreadsheet actions and low-volume workflows. It becomes a liability when it is the execution engine for mission-critical, high-volume processing. For those cases, Make.com is the right tool.
The full guide, with every step, source and date: Google Apps Script Quotas 2026 — Every Limit Explained
Originally published on Stack Architect by Luke Sandelands. Figures there carry the date they were last checked; this copy does not, so prefer the original.
Top comments (0)