Conga Contracts incident

Action Required: Refresh Salesforce Refresh Token for Conga Trigger Users

Notice Resolved View vendor source →

Conga Contracts experienced a notice incident on January 24, 2026 affecting Conga Trigger - AP and Conga Trigger - FR and 1 more component, lasting 1m. The incident has been resolved; the full update timeline is below.

Started
Jan 24, 2026, 08:22 PM UTC
Resolved
Jan 24, 2026, 08:24 PM UTC
Duration
1m
Detected by Pingoru
Jan 24, 2026, 08:22 PM UTC

Affected components

Conga Trigger - APConga Trigger - FRConga Trigger - NAConga Trigger - EU

Update timeline

  1. 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.

  2. resolved Jan 24, 2026, 08:24 PM UTC

    This was to communicate an action required for Composer Trigger users.