A recent Conga Composer update caused some organizations to be configured with a different Connected App than intended, affecting Conga Composer across NA, EU, and AP regions for approximately 8 days. The issue required manual intervention by Salesforce System Administrators to verify and correct Connected App settings, ensure proper user permissions and IP relaxation, and refresh the Salesforce Refresh Token in Conga Composer Setup. These steps successfully resolved the issue, and customers needing further assistance were directed to contact Conga Support.
With recent Composer releases, some organizations may be using a different Connected App than before. We recommend verifying which Connected App Composer is currently configured to use and confirming that its settings are correct.
Required action: A Salesforce System Administrator must complete the following steps.
Step 1: Identify the Connected App Composer is using
1. Log in to Salesforce as a System Admin.
2. Navigate to Salesforce Setup.
3. In the Quick Find box, search Custom Metadata Types.
4. Search for Conga Composer, click Composer Setting, and then click Manage Composer Setting.
5. Click Settings, and then open the Connected App Setting. For example, this may say NA Production.
6. Take note of the Connected App Name (for example, Composer NA for Salesforce).
Step 2: Verify the Connected App settings
1. In the Quick Find box, search Manage Connected Apps.
2. Click Composer NA for Salesforce.
3. Ensure Permitted Users is set to Admin approved users are pre-authorized.
4. Ensure IP Relaxation is set to Relax IP Restrictions.
5. In the Profiles section, add all Profiles that use Composer.
6. Click Save.
Step 3: Refresh the Salesforce Refresh Token
If you have not already done so, refresh the Salesforce Refresh Token from Conga Composer Setup. Even if Composer currently displays "Valid Token," refreshing the token has resolved this issue in several recent cases.
These steps have successfully resolved the error for other customers experiencing similar behavior. For additional reference, please review our Community article.
If the issue persists after completing these steps, please reply with the results and we can look into it further.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Please contact Conga Support if additional information is needed.
With recent Composer releases, some organizations may be using a different Connected App than before. We recommend verifying which Connected App Composer is currently configured to use and confirming that its settings are correct.
Required action: A Salesforce System Administrator must complete the following steps.
Step 1: Identify the Connected App Composer is using
1. Log in to Salesforce as a System Admin.
2. Navigate to Salesforce Setup.
3. In the Quick Find box, search Custom Metadata Types.
4. Search for Conga Composer, click Composer Setting, and then click Manage Composer Setting.
5. Click Settings, and then open the Connected App Setting. For example, this may say NA Production.
6. Take note of the Connected App Name (for example, Composer NA for Salesforce).
Step 2: Verify the Connected App settings
1. In the Quick Find box, search Manage Connected Apps.
2. Click Composer NA for Salesforce.
3. Ensure Permitted Users is set to Admin approved users are pre-authorized.
4. Ensure IP Relaxation is set to Relax IP Restrictions.
5. In the Profiles section, add all Profiles that use Composer.
6. Click Save.
Step 3: Refresh the Salesforce Refresh Token
If you have not already done so, refresh the Salesforce Refresh Token from Conga Composer Setup. Even if Composer currently displays "Valid Token," refreshing the token has resolved this issue in several recent cases.
These steps have successfully resolved the error for other customers experiencing similar behavior. For additional reference, please review our Community article.
If the issue persists after completing these steps, please reply with the results and we can look into it further.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with