Autocrat "Service invoked too many times": What It Means and How to Fix It
By Josh ·
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. People search for it as an Autocrat quota error or Autocrat "too many executions", and as "Autocrat stopped working" when the job dies silently. All of those come from the same family of limits.
What does the error mean? 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.
Rule out a different problem first. 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 (opens in a new tab) separately from quota errors, and reauthorizing usually clears them. And if Autocrat broke outright in June 2026, with a Rhino runtime error or a sidebar showing only Help, that was Google's forced V8 migration: what the V8 update broke and how to fix it.
Why the quota errors happen
Apps Script gives every Google account a daily budget: runtime per execution, triggers, emails sent, documents created. Merge jobs burn that budget fast. Every row opens a Google Docs document, swaps placeholders, exports a PDF, and often sends an email.
The details that catch people out are all on Google's Apps Script quota page (opens in a new tab):
- 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, but 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 Google 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 Google 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 Google Workspace account. If the job runs under a free @gmail.com account, moving the sheet and job to a paid Google 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; the 4pm failure doesn't move the clock.
For small, occasional batches, one of these will get you unstuck, and Autocrat stays a good free tool.
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 Google 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 these 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
A batch that fails every week means a weekly round of deleting rows, splitting the sheet, and waiting out the reset. SheetRender is our product. It connects to the same Google Sheets spreadsheet, 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 Google Docs merge template is the easiest starting point. Export it as a PDF, upload that as your example document, and SheetRender rebuilds it as a template already mapped to your columns. You check the mapping and repoint any field that landed on the wrong column, with no placeholders to re-tag and no code. If you'd rather keep working from a sidebar, the SheetRender add-on on the Marketplace runs the same flow from inside the sheet.
It gives up things Autocrat has. Output is PDF only. Nothing is written back to your sheet, so there is no status column showing which rows ran. The rebuilt template is a model's reading of your document, so try it on a row of live data before a batch. The quota error goes away because the merge stops running in your Google account, and the price of that is that your roster travels: to build the template we hand Anthropic the example PDF with its images, your column headers, and the top five rows of the sheet. On the free tier you can make 50 documents in a month, each with a "Made with SheetRender" footer, and nothing runs on a timer; a 51st document in the same month needs a paid plan. If your whole job is one class's certificates at the end of term, stay on Autocrat.
To see SheetRender against the other hosted tools, convert a spreadsheet to PDF automatically puts Autocrat next to them and says which of them run without you. Autocrat vs SheetRender goes through the two line by line.
For certificates specifically, the bulk certificate guide compares the ways to make them. If your trouble is Word's one-big-file merge instead, see how to split a mail merge into separate PDFs. And if you're still choosing a route, the Google Sheets mail merge guide covers the options, email merges included.