Loading
Ongoing maintenance for Salesforce HelpRead More

OmniStudio: Document Generation hangs indefinitely with no error for non-admin users

Publish Date: May 29, 2026
Description

This article explains why OmniStudio Document Generation hangs indefinitely with no error for non-admin users and how to resolve it. The symptom appears when a non-admin user clicks a Generate Document action (for example, Generate Quote) on a Quote record or launches an OmniStudio DocGen OmniScript such as CoreSingleDocxLWC: the OmniScript spinner runs indefinitely, no document is produced, and no error toast or banner is shown. The same action completes successfully when performed by a System Administrator or any user with Modify All Data. Browser console may also report a missing module such as "Definition for module 'forceGenerated/omniScript_docGenerationSample___CoreSingleDocxLWC___English___lightning___false___DefaultLabel___brand___ltr' was not found." Root causes are missing DocGen license/permission set assignments, missing access to required Apex classes and the DocGenFileUtil Visualforce page, missing read access on DocGen objects (DocumentGenerationProcess, DocumentTemplate, DocumentTemplateContentDoc, OmniDataTransform, OmniDataTransformItem), and the affected user not being a member of the Docgen Document Template Library. The issue affects OmniStudio Document Generation (DocGen) and Document Generation 2.0 in Revenue Cloud (Core) orgs on Summer '24 and later releases, in Lightning Experience and Experience Cloud, for all non-admin profiles (including standard Sales/Service profiles, Order Management profiles, and Partner/Customer Community users).

Resolution

Apply each cause below in order. After each cause, retest as the affected non-admin user before continuing.

Cause 1: Missing DocGen license and permission set assignment
1. Navigate to Setup > Users > Users and click the affected user's name.
2. Verify that the User License is set to Salesforce and the user has a Profile assigned.
3. In the Permission Set License Assignments related list, click Edit Assignments and assign DocGen User (and DocGen Designer if the user designs templates). Click Save.
4. In the Permission Set Assignments related list, click Edit Assignments and add the DocGen User permission set and the Omnistudio User permission set. Click Save.

Cause 2: User is not a member of the Docgen Document Template Library
1. Open the user's record at Setup > Users > Users, click Edit, select the Salesforce CRM Content User checkbox, and click Save.
2. From the App Launcher, open Files, click Libraries, then open Docgen Document Template Library [DocgenDocumentTemplateLibrary].
3. Click Manage Members, add the affected user (or a public group containing the user) with Viewer permission, and click Save.

Cause 3: Missing Apex class access
1. Navigate to Setup > Users > Permission Sets and open the permission set assigned to the affected user (for example, DocGen User or a custom permission set).
2. Click Apex Class Access > Edit and add the following classes: omnistudio.IntegrationProcedureService, omnistudio.BusinessProcessDisplayController, omnistudio.DocgenPostInstallClass.
3. Click Save.

Cause 4: Missing Visualforce page access (DocGenFileUtil)
1. Navigate to Setup > Users > Profiles and open the affected user's profile (or the permission set assigned to the user).
2. Click Visualforce Page Access > Edit and enable DocGenFileUtil and any other VF pages used by your DocGen OmniScripts (for example, ContractDocumentNewDisplay).
3. Click Save.

Cause 5: Missing object and field permissions for DocGen objects
1. Navigate to Setup > Users > Permission Sets and open the permission set assigned to the affected user.
2. Click Object Settings and grant Read access (Create where the user generates documents) on: Document Generation Process [DocumentGenerationProcess], Document Template [DocumentTemplate], Document Template Content Doc [DocumentTemplateContentDoc] including the LatestContentVersionId field, OmniDataTransform [OmniDataTransform], OmniDataTransformItem [OmniDataTransformItem], OmniProcess [OmniProcess], and OmniScript Saved Session [OmniScriptSavedSession].
3. Click Save.

Cause 6: Sharing settings on Omnistudio and DocGen objects
1. Navigate to Setup > Security > Sharing Settings.
2. Set the Default Internal Access for OmniProcess [OmniProcess], OmniScript Saved Session, OmniDataPack, OmniDataTransform, OmniElectronicSignatureTemplate, and DocumentGenerationProcess to Public Read Only (Public Read/Write where the user creates DocumentGenerationProcess records).
3. Click Save.

Cause 7: Server-side document generation enabled in Settings but not as an org permission (Document Generation 2.0 / Summer '24+)
1. Navigate to Setup > Feature Setting > Document Generation > Document Generation Settings and confirm that Enable Server-Side Document Generation is selected on the DocumentGenerationSetting record.
2. If using Document Generation 2.0 and the org permission for Server-Side Document Generation is not yet enabled, log a Salesforce Support case to enable the org permission. This step is required only for Document Generation 2.0 — Salesforce Support must enable the org-level toggle.

Cause 8: Experience Cloud (Partner/Customer Community) users
1. Navigate to Setup > Users > Users, open the affected community user, and assign the DocGen Runtime for Community Users permission set. Starting Winter '26, this permission set is included with Partner Community, Customer Community, and Customer Community Plus base licenses for non-industry SKUs.
2. Create a custom permission set granting Read/Create on DocumentGenerationProcess and Read on DocumentTemplate, and assign it to the community user.

Confirm the issue is resolved by logging in as the affected non-admin user, opening a Quote record, clicking the Generate Document action, and verifying that the document preview loads and the generated PDF or DOCX file is produced within the standard generation time.

Knowledge Article Number

005385099

 
Loading
Salesforce Help | Article