Conga Contracts incident
Conga Composer | Action Required: Connected App Configuration
Conga Contracts is currently experiencing a notice incident affecting Conga Composer - NA and Conga Composer - EU and 1 more component, which began 4h ago. The vendor's full update timeline is below.
Affected components
Update timeline
- monitoring Oct 05, 2026, 02:41 PM UTC
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.