Autocrat "Service invoked too many times": What It Means and How to Fix It

By Josh · July 30, 2026

If Autocrat has started failing mid-batch with "Service invoked too many times", "Exceeded maximum execution time", or jobs that just stop with no error at all, your setup probably isn't broken. You've hit one of Google's ceilings. Search calls this an Autocrat quota error or Autocrat "too many executions"; when the job dies silently, people just search "Autocrat stopped working". It's all the same family of limits.

What the error means: Autocrat runs on Google Apps Script, and your Google account hit one of Apps Script's limits: either the daily usage quota or the cap on how long a single execution can run. The merge didn't finish. The two errors have different fixes, and both are below.

First, rule out a different problem: if the error mentions authorization or permissions, that isn't a quota issue. Open the add-on, re-run its setup, and re-grant access when prompted; Google treats authorization errors separately from quota errors, and reauthorizing usually clears them.

Why the quota errors happen

Autocrat runs on Google Apps Script, and Apps Script gives every account a daily budget: runtime per execution, triggers, emails sent, documents created. Merge jobs burn that budget fast. Every row opens a Doc, swaps placeholders, exports a PDF, and often sends an email.

Three details trip people up, all documented on Google's Apps Script quota page:

Quotas are per account, not per add-on. Other scripts and add-ons on the same account eat from the same budget.
They reset 24 hours after your first request. There's no midnight reset to wait up for; the clock starts with the first run that counted against the quota.
Paid Google Workspace accounts get substantially higher quotas than free Gmail accounts. Higher, but not unlimited. No tier removes the ceilings, and there's no add-on-specific quota you can buy.

Fixes that work inside Autocrat

If the error is "Exceeded maximum execution time"

This one isn't the daily quota, and waiting a day won't help. It's the cap on how long a single Apps Script execution can run (six minutes, and paying for Workspace doesn't raise this one), and the fix is making each run smaller. Split the sheet into chunks that finish inside the window, and cut per-row work: turn off email sending (share from a Drive folder instead) and drop conditional logic you don't need. Image-heavy templates burn through the window faster.

If the error is "Service invoked too many times"

This is the daily quota. In the order I'd try them:

Delete empty rows first. Press Ctrl+End in your sheet. If the cursor lands hundreds of rows below your last real record, Autocrat is processing all of that empty space and burning quota on it. Select the empty rows, right-click, and delete rows (clearing contents isn't enough), then re-run. This is the most common reason a job that worked last month doesn't now, and it's a two-minute fix.
Check the merge status column. If rows that already merged are being picked up again, every run redoes work you already paid quota for. Make sure Autocrat is writing its status column and the job only targets unmerged rows.
Split the batch. Run smaller chunks instead of the whole sheet at once. If a run fails, try roughly half the size until runs complete reliably.
Run it from a Workspace account. If the job runs under a free @gmail.com account, moving the sheet and job to a paid Workspace account raises the daily quotas; the email-recipients cap alone goes from 100 to 1,500 a day.
Check for stuck triggers. Old time-based triggers from previous jobs keep counting against you. In Apps Script (script.google.com), remove triggers you no longer need.
Wait out the reset. The 24 hours run from your first request of the cycle. If your first merge of the day went out at 9am and things fell over at 4pm, you're clear around 9am tomorrow, not 4pm.

If your batches are small and occasional, one of these will get you unstuck. Autocrat is still a good free tool, and nothing here is a knock on it.

Common questions

How long until the quota resets? 24 hours after your first request of the cycle, so a day whose first merge ran at 9am clears at 9am tomorrow.

How many rows can Autocrat handle in one run? There's no published row limit. The practical limit is the per-execution time cap, which most people hit in the low hundreds of rows, sooner if the template is image-heavy.

Does paying for Google Workspace fix it? It helps: daily quotas are much higher on Workspace than on a free gmail.com account. The ceilings are still there, though, and the six-minute execution cap is the same on every tier.

Autocrat stopped working with no error at all. Check three things in order: empty rows below your data, an expired or revoked authorization (re-run the add-on's setup and re-grant access), and stale time-based triggers at script.google.com left over from old jobs.

If you're tired of babysitting quotas

If the batch that fails is one you run every week, the quota dance stops being worth it. That's one of the reasons we built SheetRender, so read this section knowing it's ours. It connects to the same Google Sheet, but rendering and email run on our servers instead of a long Apps Script job, so a big batch never touches your Apps Script quota.

Your existing merge Doc is the easiest starting point. Export it as a PDF, upload that as your example document, and SheetRender rebuilds it as a template mapped to your columns. No placeholders to re-tag, no code. The free plan (50 documents a month, with a small "Made with SheetRender" footer) is enough to test your setup end to end before you switch anything over. If your whole job is 30 certificates twice a year, stay on Autocrat; past 50 documents a month you're on a paid plan here. And if you want the line-by-line version, we keep a full Autocrat vs SheetRender comparison.

Merging certificates specifically? We compare four ways to do that in the bulk certificate guide. Fighting Word's one-big-file merge instead? Here's how to split a mail merge into separate PDFs.