Do not restart the full batch yet. Use a copied Google Sheet, a duplicated template, and one source row to isolate whether the failure is the tag, header, row data, file access, or output step.
Independent-product disclosure: DocForge is a FormSuite add-on. It is not affiliated with Autocrat or New Visions Cloudlab, and it does not claim full Autocrat feature parity.
The controlled proof shows a saved one-file proof, an output manifest, unchanged success reuse, changed-workflow invalidation, failed-only retry, and reconciliation.
The privacy-enhanced YouTube player loads only after you press play. Controlled Google Sheet to Google Doc proof with synthetic data.
Check tags, headers and file access on a copied Sheet; then prove one row, preserve durable proof state, review the output manifest, retry failed rows only, and reconcile the batch.
The privacy-enhanced YouTube player loads only after you press play. Controlled copied-sheet and duplicate-template tutorial with synthetic data.
Spaces, punctuation, capitalization, and hidden trailing characters can make a tag look correct while it points to no column. Copy the header text directly into the template tag for the one-row test.
Confirm the test row is not filtered out, the required cells are not blank, and formulas have finished calculating. Do not infer the result from a different row.
Open the exact Google Docs template and output folder from the same account running the merge. A moved, deleted, or inaccessible file can look like a placeholder problem.
Keep the live job unchanged. A copied-Sheet test removes the risk of duplicate production files while you isolate the failing mapping.
Use an order, invoice, certificate, member, or case ID when available. Duplicate or blank keys should block Preflight instead of weakening duplicate protection.
A changed template version, header set, mapping, stable key, naming pattern, folder, or output must invalidate the previous proof.
Do not generate an accessible unchanged output twice. Show missing, changed, and failed states instead of silently hiding them.
Retry only failed rows, then compare expected, generated, reused, changed, and failed totals.
You have one Google Docs template, stable Sheet headers, a copied file for testing, and you want an exact one-row preview before generating one output.
Do not assume support for every Autocrat trigger, multi-template job, attachment, conditional route, approval, or distribution feature. Keep the existing workflow until the narrow copied-file test succeeds.
A sidebar message alone is not proof. The file must open with the copied-row values, the saved proof must still match the workflow, and the reconciliation must explain generated, reused, changed, and failed rows. Internal QA is product evidence, not a customer success signal.
Check exact tag-to-header matching, the selected Sheet tab, blank source cells, template access, and the specific row being merged. Test one copied row before changing the live job.
No. Generate and open one file first. A full rerun can create duplicates without proving the mapping is fixed.
No. DocForge is independent and is positioned for a narrow single-template, one-row proof—not universal feature parity.
Keep successful outputs unchanged, repair the failing source or mapping, retry failed rows only, and review the reconciliation totals before another production run.