Horus Eye · Nintex[1] DocGen
Most Nintex DocGen troubleshooting ends at one of these: the issues that actually stop documents, embarrass e-mail sends, and quietly multiply maintenance in DocGen (Loop) estates — whether yours was installed last year or back when the package was called Drawloop. For each: what it may mean, how to fix it, and whose hands make the change — because the honest answer is sometimes “yours”, sometimes “your DocGen admin’s”, and sometimes “it can be applied for you once you decide”.[2]
What it may meanGeneration fails or returns no data
How to fix it MConfirm whether the object exists; point the relationship at the right object, remove it, or grant the scanning user access — then re-scan
DocGen admin
What it may meanGeneration fails at run time
How to fix it SReattach or remove the template; generate once; re-scan
DocGen admin
What it may meanThe package cannot start
How to fix it MRe-point the starting object, or retire the package
DocGen admin — or applied for you once your decision is recorded
What it may meanNo finished document
How to fix it SAdd the missing piece, or retire the package
DocGen admin
What it may meanUsers pick the wrong one
How to fix it MName the keeper; move unique templates and options into it; retire the copies (set inactive, reversibly — nothing deleted)
You decide; applied after your answer
What it may meanTest output reaches real recipients
How to fix it XSRetire them, or rename them if they are real
You decide; applied after your answer
What it may meanMore to maintain; user confusion
How to fix it MConsolidate to one package
DocGen admin
What it may meanE-mails go out empty or inconsistent
How to fix it XSFill the subject or body you approve — a one-field write, previewed with its before-value and reversible
You decide; applied after your answer
What it may meanWording drifts apart across options
How to fix it SChoose a Salesforce e-mail template so the wording lives in one place
You decide; DocGen admin applies
What it may meanUsers guess which option to use
How to fix it XSApprove the help text once; it is written for you
You decide; applied after your answer
What it may meanUsers don’t recognize it
How to fix it SPick one word and use it everywhere
You decide; applied after your answer
What it may meanDepends on storage being retired
How to fix it MPlan the move to Files; storage settings can be switched one option at a time, reversibly
You decide; applied after your answer
What it may meanSecurity and compatibility risk — and the macros do not run during generation anyway
How to fix it SSave in the standard format unless the macro is genuinely needed
DocGen admin
What it may meanContradictory settings
How to fix it XSAlign the two settings
DocGen admin
What it may meanSlow, heavy generation
How to fix it MUse conditional content, or split the package
DocGen admin
Where a fix is applied for you, it is one allowlisted field on an existing DocGen record: previewed with its before-value, confirmed by you, read back after writing, and reversible on request. A fix counts as verified only when the rule that raised it goes silent on the next scan — not when the change is made.
About the figures on this page: counts and percentages describe Horus Eye’s own test orgs, which hold seeded example data. They are examples of what an assessment reports — never typical results and never a benchmark for your org.
Salesforce Help · Migrate to Flow Tool — Salesforce’s path off workflow rules and Process Builder — the context for modernizing legacy outbound-message automation. ↩︎“Salesforce”, “Agentforce” and related marks are the property of Salesforce, Inc. Nintex and DocGen are marks of Nintex. Horus Eye is an independent product and is not affiliated with, endorsed, or sponsored by Salesforce, Inc. or Nintex.
Every AI read in Horus Eye is metadata-first: built from an allowlist, sanitized by pattern, made through one audited gateway and checked by an output firewall on the way back — and AI is off by default, per org. Every request carries an audit id and an AI Data Scope manifest you can open.
A read-only assessment counts them with evidence, package by package, and sorts them into what you decide, what gets applied for you, and what needs the DocGen admin.
Try Horus Eye Free Request a DocGen Assessment All Horus Eye pagesFree start · 250 credits for 60 days · no card required · scans are free