Google Apps Script · Quotas · 2026 Limits
The exact quota numbers for consumer and Workspace accounts in 2026, why they break Autocrat and Sheets automations, and the structural fix that scales past them.
You have hit a quota limit. Here is exactly which one and how to fix it — free, no upgrade required, works at any order volume.
Quick answer — the numbers that matter in 2026: Consumer (free) Google accounts get a 6-minute maximum execution time per script run and 90 minutes of total daily runtime. Google Workspace accounts get 30 minutes per execution and 6 hours of daily runtime. UrlFetch calls are capped at 20,000 per day on consumer accounts. These are the hard limits that cannot be increased — they are why Autocrat, Sheets automations, and document workflows fail at scale.
If you have ever seen “Service invoked too many times”, “Exceeded maximum execution time”, or “Could not obtain lock”, you already know the symptom. This guide explains the exact numbers behind those errors, when they appear by account type, and what actually works when order or document volume gets serious.
Shopify Stocky shuts down August 31, 2026. The free replacement — Stocky Swap — logs every order to Google Sheets via Make.com, bypassing Apps Script quota limits entirely. Deploys in 4 minutes. Don't wait until August.
Google Apps Script quotas are hard limits on how much work a script can do. They exist to protect shared infrastructure — stopping one workflow from consuming resources that affect thousands of other users. Quotas appear across four layers, and they all apply simultaneously:
The critical point is that these limits stack independently. A workflow can be fine on execution time but fail on service call rate — which is why the same script can work perfectly for a small operation and break as soon as volume rises.
These are the official limits as of April 2026. Google does not announce changes widely — they update the quotas page without notice, which is why searches for “quotas 2026” are so common.
A single script run on a free Google account is hard-stopped after 6 minutes. This is the most common cause of incomplete document generation and partial Sheets processing.
Google Workspace accounts get 30 minutes per execution. Still a hard ceiling — but five times more headroom for large batch jobs.
Total combined runtime across all script executions per day on a free account. Once exhausted, all scripts for that account stop until midnight Pacific Time.
Google Workspace accounts get 6 hours of combined daily execution time. Sufficient for most high-volume automation stacks, though not unlimited.
Hits this ceiling faster than expected when automations check external APIs (Shopify webhooks, tracking endpoints, third-party services) on every order.
Five times more headroom. Still a per-day hard limit. Burst usage in the first hour can exhaust this before the day ends.
Calls to Google Docs or Drive in any rolling 60-second window. Autocrat-style workflows that open, fill, and save documents hit this quickly on medium batches.
All daily quotas reset at midnight Pacific Time — not your local timezone. Workflows that fail late in your day may recover before your next working morning.
The 6-minute vs 30-minute execution gap is the single biggest reason to upgrade to Google Workspace for automation-heavy operations. If your Shopify order volume means scripts regularly hit the 6-minute ceiling, the upgrade decision covers the exact trigger point and $21/month cost calculation in our Upgrade Guide.
| Quota Type | Consumer (free) | Google Workspace | Resets |
|---|---|---|---|
| Single execution time | 6 minutes | 30 minutes | Per run |
| Daily total runtime | 90 minutes | 6 hours | Midnight PT |
| UrlFetch calls/day | 20,000 | 100,000 | Midnight PT |
| Document creates/day | 250 | 1,500 | Midnight PT |
| Email recipients/day | 100 | 1,500 | Midnight PT |
| Concurrent executions | 30 | 30 | Per moment |
| Script properties size | 500KB | 500KB | Persistent |
Quota failures are rarely random. They follow predictable patterns based on four root causes:
Simple scripts under 100 rows/day usually stay inside quota with basic monitoring.
Once volume scales past a few hundred rows per day, batching and timing become essential.
When the workflow is mission-critical and volume is unpredictable, shared Apps Script limits are the wrong architecture.
Each error message maps to a specific quota breach. Knowing which limit you hit tells you which fix applies.
| Error Message | Quota Breached | Immediate Cause |
|---|---|---|
| Service invoked too many times | Service call rate | Too many calls to Sheets, Docs, Drive, or Gmail in a short window |
| Exceeded maximum execution time | 6-min / 30-min ceiling | Single run took longer than allowed — script hard-stopped mid-execution |
| Could not obtain lock | Concurrent execution | Two runs tried to access the same resource simultaneously |
| Quota exceeded | Daily service limit | UrlFetch, document creates, or email sends hit the daily cap |
| Daily limit for sending email exceeded | 100/day consumer cap | Email sends exhausted before end of day |
If “Service invoked too many times” is your specific error, the fix steps differ from other quota errors. The step-by-step fix guide covers each scenario with the specific code patterns that stop the error at its root cause.
If your quota errors are tied to Shopify order volume — particularly inventory sync or order logging workflows — the Stocky Swap free replacement routes every order through Make.com directly to Google Sheets, bypassing Apps Script execution entirely. No quota ceiling, no 6-minute limit, no document create cap. Deploy free in 4 minutes →
These six techniques reduce quota pressure and can sustain most medium-volume automations on consumer accounts. They are mitigation strategies — not architectural solutions for serious scale.
getValues() once, operate on the array in memory, then write back with a single setValues() call.Batching and backoff can take a stable 100-row workflow and scale it to 500 rows. They cannot take a 500-row workflow to 5,000 rows. At that point, the daily runtime ceiling is the binding constraint — and no code optimisation changes a 90-minute daily limit.
Autocrat · Document Automation · Quota Fix
Autocrat is one of the most popular document generation tools for Google Sheets — and one of the most quota-sensitive. If you are generating contracts, invoices, certificates, or any templated document from Sheets rows, you will hit quota limits earlier than almost any other Apps Script workflow.
Each Autocrat document generation triggers multiple service calls in sequence: it opens Google Drive, reads the template, creates a new document, writes merged data into it, converts to PDF if needed, saves to Drive, and optionally sends via Gmail. That is 5–8 service calls per row. At 30 document service calls per minute (consumer limit), Autocrat can reliably process around 4–5 documents per minute — or roughly 25–30 in a single run before the service rate limit triggers.
The reliable solution is moving document generation off Google's shared execution environment entirely. Instead of Autocrat running inside Apps Script on Google's public quota pool, the workflow runs through a dedicated Make.com scenario that calls the Google Docs API directly via a private HTTP connection.
The Autocrat Quota Fix product page has the Make.com scenario blueprint, step-by-step alignment instructions, and the deployment guide — no coding required, ready in under 15 minutes.
The signal is usually obvious: document generation starts missing rows, order sync gets delayed, or the workflow behaves differently depending on the time of day. That last symptom — time-dependent behaviour — is the clearest sign of a daily quota problem.
Keep lightweight logic close to the spreadsheet — change detection, simple calculations, notification sends — and move heavy lifting to a system built for throughput.
Apps Script detects the event. Make.com or a dedicated service does the processing. The result lands back in Sheets. This pattern removes the quota ceiling from every expensive operation. The Make.com for Shopify complete guide covers exactly how to set this up from scratch.
What is the Google Apps Script execution time limit in 2026?
Consumer (free) Google accounts are capped at 6 minutes per execution. Google Workspace accounts get 30 minutes per execution. 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?
Consumer accounts get 90 minutes of combined runtime per day. Google Workspace accounts get 6 hours per day. Once the daily limit is exhausted, all scripts for that account stop executing until the quota resets at midnight Pacific Time.
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 consumer execution, 30-minute Workspace execution, 90-minute daily consumer runtime — have remained consistent. Google does not announce quota changes prominently. If you are seeing new failures in 2026, 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?
No. The limits are set by Google at the infrastructure level and cannot be increased by request, payment, or configuration. The only way to operate above the hard ceilings is to move the work outside of Apps Script execution — 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. Your automations are exhausting the 90-minute daily runtime in the first half of the day, leaving nothing for afternoon processing. The quota resets at midnight Pacific Time — which is why everything works again the next morning.
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.
Google Apps Script quotas in 2026 are not a mystery once you know the numbers: 6 minutes per execution, 90 minutes per day, 20,000 UrlFetch calls on a consumer account. They are clear, fixed, and cannot be negotiated with. If your automation is stable, the limits are irrelevant. If your workflow is growing, the limits become the ceiling.