Conga Contracts incident
Action Required: Refresh Salesforce Refresh Token for Conga Trigger Users
Resolved after 1 minute, affecting Conga Trigger - AP and Conga Trigger - FR and 1 more, on January 24, 2026.
Following our recent upgrade, Conga Trigger now uses OAuth instead of the legacy Session ID included in the Salesforce outbound message. To restore automation functionality, all Conga Trigger users must refresh their Salesforce Refresh Token. Steps to refresh your token: 1) Log into Salesforce as a System Administrator. 2) Open the App Launcher (upper-right, 9-dots icon). 3) In the Quick Find search box, enter: Conga Batch Setup or Conga Trigger Setup. 4) Select Conga Batch Setup or Conga Trigger Setup. 5) Open the Credentials tab. 6) Click “Update Salesforce Token.” 7) Verify that the status displays “Valid Token” in green. Please reach out to support if any further help is needed.
Affected components
Update timeline
- investigating Jan 24, 2026, 08:22 PM UTC
Following our recent upgrade, Conga Trigger now uses OAuth instead of the legacy Session ID included in the Salesforce outbound message. To restore automation functionality, all Conga Trigger users must refresh their Salesforce Refresh Token. Steps to refresh your token: 1) Log into Salesforce as a System Administrator. 2) Open the App Launcher (upper-right, 9-dots icon). 3) In the Quick Find search box, enter: Conga Batch Setup or Conga Trigger Setup. 4) Select Conga Batch Setup or Conga Trigger Setup. 5) Open the Credentials tab. 6) Click “Update Salesforce Token.” 7) Verify that the status displays “Valid Token” in green. Please reach out to support if any further help is needed.
- resolved Jan 24, 2026, 08:24 PM UTC
This was to communicate an action required for Composer Trigger users.
Your product runs on more than Conga Contracts
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services