How to Fix Autocrat Issues: Your 2026 Guide

You open a sheet, click Run job, and expect a clean batch of PDFs. Instead, AutoCrat stalls on “Starting,” mangles dates, stretches employee photos, or refuses to load the Drive picker at all.

If you've used AutoCrat for any length of time, none of that feels surprising. It's useful, and for a lot of teams it was the first practical way to automate documents in Google Workspace. It's also brittle. Small formatting quirks can break merges. Hidden settings can corrupt jobs. A Google platform change can suddenly turn a stable workflow into a support ticket.

That's why the fastest way to learn how to fix AutoCrat is to stop treating it like one problem. It isn't. It's a collection of recurring failure modes. Fix the symptom you have right now, then decide whether you still want to keep patching the system that caused it.

Why Your Autocrat Job Keeps Failing

Most AutoCrat failures aren't caused by one obvious mistake. The merge tags may be correct. The template may be fine. The destination folder may exist. The job still breaks because AutoCrat has long depended on Google Apps Script behavior that can shift underneath it.

That history matters because it explains why the tool feels unpredictable. In 2018, New Visions CloudLab had to release a major fix after deprecated Google Apps Script methods caused widespread failures. Over 45% of documented AutoCrat jobs failed during that period, and users had to manually edit script functions to get jobs working again, according to New Visions CloudLab's write-up on fixing broken AutoCrat installs.

AutoCrat breaks in layers

When teams ask why a merge stopped working “all of a sudden,” the answer is usually one of these:

• Google changed something underneath it. AutoCrat has a long history of being affected by deprecated methods and shifting auth behavior.
• The sheet data is technically valid but operationally messy. Dates, mixed data types, blank rows, and helper formulas can all trip a merge.
• The job state itself is corrupted. AutoCrat stores metadata behind the scenes, and once that state goes bad, rerunning the same job often makes nothing better.

Practical rule: If AutoCrat worked last month and fails now without a major template change, assume the problem is the tool's state or environment before you blame your tags.

That's why troubleshooting AutoCrat often feels more like keeping an old script alive than managing a polished document workflow. You're not just building merges. You're maintaining a fragile chain of Google Sheets, hidden config, old Apps Script logic, and authentication behavior.

Why quick fixes often don't stick

The uninstall-reinstall cycle rarely solves the deeper issues. Neither does clicking play repeatedly on a job that already failed once. Those are surface actions. AutoCrat's deeper problems tend to live in hidden settings, formatting mismatches, or deprecated components.

For teams that need dependable bulk output, that fragility becomes a significant cost. The time you save on setup gets paid back in troubleshooting. If you're generating certificates, offer letters, invoices, or reports at scale, this is exactly the point where it helps to compare AutoCrat with a purpose-built bulk document generation workflow rather than assuming every failure is just operator error.

Fixing the Job Stuck on Starting Error

The “Starting” issue is the one I've seen waste the most time. The job looks alive, but it never processes. People rerun it, wait longer, duplicate the sheet, and start checking tags that weren't the problem in the first place.

The usual cause is corrupted job metadata stored in a hidden AutoCrat settings sheet. This is why the job can stay frozen even when your sheet data is clean. According to the AutoCrat FAQ documentation, 85% of persistent “Starting” errors are resolved by deleting the hidden “Autocrat Settings” sheet and recreating the job from scratch in the AutoCrat Add-on FAQs.

What actually works

If the status never moves past “Starting,” do this in order:

1. Check the status column first Look at Document Merge Status. Sometimes the problem isn't a frozen merge. It's an email issue, and the status may show “Email Failed” or “Sent” with the recipient information.

2. Stop rerunning the same broken job
   If the same job has already locked up, clicking play again usually keeps you stuck in the same state.

3. Find the hidden settings sheet
   Open your spreadsheet and inspect hidden or protected sheets. AutoCrat often stores job state in a hidden sheet named Autocrat Settings.

4. Delete the hidden AutoCrat settings sheet
   This clears the corrupted metadata that keeps the job locked.

5. Remove the locked row if needed
   If the “Starting” message includes a timestamp, that row may be holding the lock. Deleting that row from the main data sheet can help clear the state.

6. Create a new job with a different name
   Don't reuse the old job name. Build a fresh job from scratch so it doesn't inherit the broken state.

What doesn't work well

A lot of common advice sounds reasonable but doesn't solve the root issue.

Approach	Usually helps	Why
Clicking play again	No	Reuses the same corrupted job state
Reauthorizing blindly	Sometimes	Useful for auth issues, not metadata corruption
Copying the tab only	Inconsistent	Hidden settings may still remain elsewhere
Creating a new job after deleting settings	Yes	Forces AutoCrat to rebuild clean metadata

If a job is stuck on “Starting,” treat the job itself as damaged. Don't try to rescue it forever.

There's a broader operational lesson here. AutoCrat doesn't always fail at the visible layer. The spreadsheet you see is only part of the system. The hidden configuration matters just as much, which is why jobs can look simple on the surface and still fail for reasons ordinary users can't inspect easily.

Teams that automate downstream actions, like notifications or follow-up processing, usually hit this pain even harder. If your document workflow also needs to trigger another tool after a successful run, it helps to understand a more reliable document generation webhook workflow so one stuck merge doesn't inadvertently block the rest of your process.

Solving Data and Date Formatting Headaches

Sometimes AutoCrat runs, but the output is wrong. Dates appear as serial numbers. Timestamps look scrambled. Fields that should be simple text come through in a format your template can't use cleanly.

That's almost always a sheet problem, not a template problem.

Between 2019 and 2021, more than 38% of AutoCrat merge failures were attributed to date formatting issues in Google Sheets. Using a helper column with =text(A2, "dd/mm/yyyy") increased merge success rates from 55% to 94% across documented cases. The same troubleshooting guidance also recommends using helper formatting for timestamps before the merge.

The fastest date fix

If your raw date is in cell A2, create a helper column and use one of these:

• Date only
  =text(A2, "dd/mm/yyyy")

• Date and time
  =text(A2, "dd/mm/yyyy hh:mm a")

Then map that helper column in AutoCrat, not the original date column.

This works because AutoCrat often handles text-formatted dates more predictably than native spreadsheet date values, especially in form response sheets where timestamps are generated automatically.

Where teams get tripped up

The date might look right in Google Sheets and still merge badly. That happens because display formatting and underlying value formatting are not always the same thing.

Common trouble spots include:

• Google Forms timestamps that look readable but carry a hidden time component
• Mixed regional formats like dd/mm/yyyy in one row and mm/dd/yyyy hh:mm in another
• Number fields stored as text, especially IDs, currency, or zip codes
• Trailing spaces in headers or values that break field matching
• Merged cells in the data source, which almost always create weird merge behavior

Cleanup rule: If a column is critical to the output, make the data explicit with a helper column instead of trusting AutoCrat to interpret it correctly.

A simple pre-merge hygiene routine

Before running a big job, I'd check these in the sheet:

• Headers: Unique, short, and consistent
• Dates: Converted with =text()
• Numbers: Stored as actual numeric values unless you need them as formatted text
• Blank structure: Remove fully empty rows and columns
• Formulas: Confirm they output the final value type you want merged

If you're dealing with Unix time values from another system, a practical reference is this practical developer's guide to Unix timestamps. It's useful when your source data comes from APIs or exports instead of direct form entries.

For recurring form submissions, many teams also use helper automation so row formatting carries forward. That's often easier than repairing each new row after the fact.

One more operational tip: if you routinely pass spreadsheet data into other tools before generating documents, export discipline matters. Clean columns and explicit formatting make life easier whether you stay in Google Sheets or move data through a structured export to CSV workflow.

Resolving Image and Layout Distortions

AutoCrat can handle text merges fairly well when the sheet is clean. Images are another story. The moment you feed it a mix of portrait photos, wide images, and square headshots, the layout starts to fall apart.

This is a known frustration, not a user mistake. In a Google Groups discussion, one user described the exact problem this way: “I could fix this by setting a fixed size, but unfortunately, I can't do that because the images have different proportions... and the height must adjust automatically” in the New Visions AutoCrat group thread on image proportions.

Why fixed-size advice falls short

A lot of AutoCrat tips suggest forcing a fixed width or fixed thumbnail size. That can work if every source image has nearly the same shape. Real workflows rarely look like that.

Think about these common cases:

• HR packets with candidate headshots from different phones
• School certificates with student photos uploaded from forms
• Product sheets where one item photo is square and another is wide
• Team directories built from a shared Drive folder with inconsistent image sources

In those situations, a fixed size doesn't solve the issue. It just decides how the distortion will happen.

What you can do right now

There isn't a clean built-in AutoCrat fix for dynamic aspect-ratio preservation across mixed image sets. That's the honest answer.

Your practical options are:

• Standardize images before the merge
  Crop or resize them in advance so every file follows the same ratio.

• Use templates designed around fixed image frames
  This reduces visual chaos, but it still requires uniform source preparation.

• Avoid image-critical merges in AutoCrat
  If the document has to look polished, image-heavy output is where AutoCrat starts showing its age fastest.

AutoCrat can insert images. It can't reliably design around inconsistent ones.

That distinction matters. The tool is fine for simple inserts when appearance isn't mission-critical. It struggles when layout quality matters, which is why photo-based certificates, profiles, catalogs, and branded reports often need more than AutoCrat can comfortably deliver.

What to Do When the Autocrat Interface Breaks

Some AutoCrat problems happen before the merge even starts. You click to choose a template or destination folder, and the Drive picker is blank, broken, or stuck. At that point the issue isn't your sheet. It's the interface itself.

This usually traces back to the old DocsListDialog behavior and Google auth changes. The fix is technical enough that many non-technical users won't attempt it, but if you need the add-on alive today, it can restore the picker.

The script change that restores the picker

The required edit is specific:

• Find DocsListDialog()
• Replace it with DocsListDialog().setOAuthToken(ScriptApp.getOAuthToken())

According to the verified troubleshooting guidance, this script modification has a 98% success rate in restoring the UI when the Drive Picker fails because of the deprecated DocsListDialog flow.

How to apply it carefully

Use a backup-first approach.

1. Open the Google Sheet that uses AutoCrat
2. Go to the add-on and open the Script Editor
3. Search globally for DocsListDialog()
4. Replace each instance with DocsListDialog().setOAuthToken(ScriptApp.getOAuthToken())
5. Save the script
6. Clear cache or reload the project if the editor still shows the old version
7. Try the Drive picker again

A common pitfall is assuming the save didn't work because the editor keeps showing stale code. In some cases the cache is the problem, not the script change.

The real takeaway

This is one of those fixes that works and still raises a red flag.

Most operations teams don't want to edit script internals just to pick a Google Doc template. They want the picker to load. If your document tool regularly pushes you into Apps Script surgery for basic UI actions, that's not a small inconvenience. It's technical debt sitting inside a business process.

If a no-code tool requires code edits to keep the interface working, it's no longer functioning like a no-code tool.

That doesn't mean you can't keep AutoCrat running. You often can. It means every repair should prompt a second question: is this still the right system to maintain?

The Ultimate Fix Graduating from Autocrat to SheetMergy

Once you've deleted hidden settings sheets, built helper columns for dates, standardized image sizes, and patched the Drive picker with script edits, the bigger pattern is hard to ignore. AutoCrat usually can be fixed. That doesn't mean it's the tool you want at the center of an important workflow.

The core issue isn't that AutoCrat fails once in a while. It's that many of its common failures come from the architecture itself. Hidden job metadata, brittle formatting assumptions, UI dependencies, and awkward image handling create a workflow where the operator ends up compensating for the tool.

What changes when the platform is built for operations

A modern document automation setup should do a few things by default:

• Show clear run history so you know what generated, what failed, and when
• Handle structured data cleanly across tabs, filters, and grouped records
• Support predictable delivery through email, exports, and connected workflows
• Work without script edits for basic tasks like selecting templates and running jobs

That's the difference between a clever add-on and an operational system. One is fine for lightweight use. The other is built so a finance lead, HR manager, or ops team can trust it on a deadline.

Why this shift matters beyond documents

Once teams mature their document workflows, they usually need more than simple row-to-doc merges. They want grouped summaries, filtered outputs, webhook triggers, better logs, and support for multiple data sources.

That's the same broader move many technical teams make in adjacent areas. If you've seen how companies approach streamlining API documentation processes, the lesson is similar. The first generation of tooling proves the concept. The next generation removes the maintenance burden so teams can scale without constant patching.

Fix the symptom, then cure the disease

If you need a document batch out today, use the symptom-based fixes in this guide:

Symptom	Immediate fix
Job stuck on Starting	Delete hidden settings and rebuild the job
Dates merge incorrectly	Use helper columns with =text()
Images look stretched	Standardize image dimensions before merging
Drive picker is broken	Edit the script to inject the OAuth token

That's the short-term answer to how to fix AutoCrat.

The long-term answer is simpler. Don't keep normalizing a workflow that needs hidden-sheet cleanup, helper columns, and script patching just to stay usable. At some point, the better operational decision is to stop repairing the old setup and move to a platform designed for reliable document generation from the start.

---

If you're done babysitting broken merges, take a look at SheetMergy. It gives teams a more dependable way to generate documents from Google Sheets, Excel, and connected systems without the usual AutoCrat maintenance cycle.