Please contact Conga Support if additional information is needed.

<p>With recent Composer releases, some organizations may be using a different <strong>Connected App</strong> than before. We recommend verifying which Connected App Composer is currently configured to use and confirming that its settings are correct.</p> <p><strong>Required action:</strong> A Salesforce System Administrator must complete the following steps.</p> <p><strong>Step 1: Identify the Connected App Composer is using</strong><br> 1. Log in to Salesforce as a System Admin.<br> 2. Navigate to <strong>Salesforce Setup</strong>.<br> 3. In the Quick Find box, search <strong>Custom Metadata Types</strong>.<br> 4. Search for <strong>Conga Composer</strong>, click <strong>Composer Setting</strong>, and then click <strong>Manage Composer Setting</strong>.<br> 5. Click <strong>Settings</strong>, and then open the <strong>Connected App Setting</strong>. For example, this may say <em>NA Production</em>.<br> 6. Take note of the Connected App Name (for example, <em>Composer NA for Salesforce</em>).</p> <p><strong>Step 2: Verify the Connected App settings</strong><br> 1. In the Quick Find box, search <strong>Manage Connected Apps</strong>.<br> 2. Click <strong>Composer NA for Salesforce</strong>.<br> 3. Ensure <strong>Permitted Users</strong> is set to <strong>Admin approved users are pre-authorized</strong>.<br> 4. Ensure <strong>IP Relaxation</strong> is set to <strong>Relax IP Restrictions</strong>.<br> 5. In the <strong>Profiles</strong> section, add all Profiles that use Composer.<br> 6. Click <strong>Save</strong>.</p> <p>These steps have successfully resolved the error for other customers experiencing similar behavior. For additional reference, please review our <a href="https://community.conga.com/composer-how-to-13/connected-app-name-changes-after-composer-8-298-update-9506?tid=9506&fid=13">Community article</a>.</p> <p>If the issue persists after completing these steps, please reply with the results and we can look into it further.</p>