Conga Contracts Outage History

Started Feb 23, 2026, 11:00 AM UTC· resolved Feb 24, 2026, 01:20 AM UTC

1. investigating Feb 23, 2026, 11:20 AM UTC

   We are currently investigating reports of errors or failures for a few operations when using X-author addin. We will provide further updates as they are available.

2. investigating Feb 23, 2026, 12:18 PM UTC

   Our engineers are currently investigating reports of affecting X-author for Contracts within the NA and EU regions. Customers may experience inability to access X-Author for Contracts. We will provide further updates as they are available.

3. identified Feb 23, 2026, 02:33 PM UTC

   We've identified the root cause of the issue which stems from an administrative error on the Microsoft Partner Portal. We're working closely with Microsoft Support to restore services. Customers may continue to experience inability to access X-Author for Contracts while the fix is being deployed.

4. identified Feb 23, 2026, 04:03 PM UTC

   This issue stems from an error that inadvertently delisted the product from the Microsoft Partner Portal. We continue to work with Microsoft Support to restore the listing. At this time, there is no workaround or action required on your end. We are actively pushing for a resolution and will provide another update as soon as we receive more information from Microsoft. Thank you for your patience.

5. identified Feb 23, 2026, 05:26 PM UTC

   We are actively coordinating with the Microsoft Marketplace escalation and engineering teams to expedite the restoration of the service.

6. identified Feb 23, 2026, 06:42 PM UTC

   We are continuing to work directly with Microsoft to restore Conga X-Author services. This issue has been escalated to the highest priority within the Microsoft queue. At this time, Microsoft has provided an estimated time to resolution of 2 to 5 hours. We are monitoring the situation closely and will notify you as soon as service is restored, or if there are any changes to this timeline.

7. identified Feb 23, 2026, 07:45 PM UTC

   Microsoft is currently continuing the certification process to restore the Conga X-Author service. To assist with a rapid recovery, our team has provided Microsoft with test environments to actively validate the service as it comes back online. We are monitoring this validation process closely and will provide a further update once the service is fully restored. Thank you for your continued patience.

8. identified Feb 23, 2026, 08:23 PM UTC

   Conga X-Author for Contracts in the NA region has successfully completed validation and is now live. The remaining Conga X-Author applications are currently pending final certification by Microsoft. We will continue to monitor the progress closely and send another update once the remaining X-Author services are restored.

9. identified Feb 23, 2026, 09:42 PM UTC

   X-Author Contracts in the EU region has successfully completed validation and is now live. The remaining Conga X-Author applications are currently pending final certification by Microsoft. We will continue to monitor the progress closely and send another update once the remaining X-Author services are restored.

10. identified Feb 23, 2026, 10:25 PM UTC

    X-Author Contracts in the NA region has successfully completed validation and is now live. The remaining Conga X-Author applications are currently pending final certification by Microsoft. We will continue to monitor the progress closely and send another update once the remaining X-Author services are restored.

11. identified Feb 24, 2026, 01:00 AM UTC

    Conga X-Author for Contracts in EU and FR region are currently pending final certification by Microsoft. We're continuing to monitor the progress closely and send another update once services are restored.

12. resolved Feb 24, 2026, 01:24 AM UTC

    The Microsoft certification process is complete, and all Conga X-Author services have been restored. If you continue to experience issues or have further questions, please contact Conga Technical Support to raise a support case so our team can assist you directly. Thank you for your patience.

Read the full incident report →

Started Jan 25, 2026, 03:30 AM UTC· resolved Jan 25, 2026, 05:47 AM UTC

1. investigating Jan 25, 2026, 04:56 AM UTC

   We are currently investigating issues with intermittent failure affecting Platform Login within the EU Region Customers may experience a failed login. We will provide further updates as they are available.

2. identified Jan 25, 2026, 05:12 AM UTC

   The issue has also impacted APAC region. The issue has been identified and is do to a timing of a certification rotation. The issue should be resolved within the hour.

3. monitoring Jan 25, 2026, 05:42 AM UTC

   Logins are now passing and we will continue to monitor.

4. resolved Jan 25, 2026, 05:47 AM UTC

   The issue impacting Platform Login in the EU and APAC has been fully resolved and all affected systems have returned to normal operation.

Read the full incident report →

Started Jan 24, 2026, 08:22 PM UTC· resolved Jan 24, 2026, 08:24 PM UTC

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.

Read the full incident report →

Started Jan 22, 2026, 08:19 PM UTC· resolved Jan 23, 2026, 09:55 AM UTC

1. investigating Jan 22, 2026, 08:19 PM UTC

   We are currently investigating reports of login failures affecting customers using Conga IDP for Advantage Platform authentication in all regions. Customers may experience issues receiving OTPs, preventing successful authentication. This issue is limited only to Conga IDP at this time. We will provide further updates as they are available.

2. identified Jan 22, 2026, 09:06 PM UTC

   We've identified the root cause of the issue is resulting from a confirmed Microsoft 365 service outage. This issue is strictly limited to the Conga IDP flow. All other authentication methods to the Advantage Platform remain fully functional. We are closely monitoring Microsoft's remediation progress and will update this page as their services recover. Microsoft Outage Status: https://status.cloud.microsoft/

3. identified Jan 22, 2026, 09:55 PM UTC

   We are continuing to monitor the ongoing Microsoft service incident which is impacting OTP delivery for Conga IDP logins. There has been no change to the scope of impact. Microsoft Outage Status: https://status.cloud.microsoft/

4. identified Jan 22, 2026, 11:01 PM UTC

   We are continuing to monitor the ongoing Microsoft service incident which is impacting OTP delivery for Conga IDP logins. There has been no change to the scope of impact. We want to reiterate that all other login methods remain fully operational. We are tracking Microsoft's remediation efforts closely and will provide the next update in one hour or as soon as a resolution is confirmed. Microsoft Outage Status: https://status.cloud.microsoft/

5. identified Jan 22, 2026, 11:58 PM UTC

   We are continuing to monitor the ongoing Microsoft service incident which is impacting OTP delivery for Conga IDP logins. There has been no change to the scope of impact. Microsoft Outage Status: https://status.cloud.microsoft/

6. identified Jan 23, 2026, 01:09 AM UTC

   We are continuing to monitor the ongoing Microsoft service incident which is impacting OTP delivery for Conga IDP logins. There has been no change to the scope of impact. We've observed our internal tests passing intermittently as Microsoft continues recovery efforts. We are tracking Microsoft's remediation closely and will provide the next update as a resolution is confirmed. Microsoft Outage Status: https://status.cloud.microsoft/

7. resolved Jan 23, 2026, 09:55 AM UTC

   We have confirmed that the Microsoft service outage has been fully resolved. We have been closely monitoring all our automated helath checks and they're all passing successfully for the past few hours.

Read the full incident report →

Started Jan 10, 2026, 04:38 AM UTC· resolved Jan 10, 2026, 07:45 AM UTC

1. investigating Jan 10, 2026, 04:38 AM UTC

   Sign 2.0 services on Conga Advantage Platform for APAC region are down. Sign dashboard, Sign connector, Sign APIs are currently down.

2. identified Jan 10, 2026, 06:27 AM UTC

   Issue seems to be on the account of OneSpan maintenance. Conga team is closely working and following up with OneSpan support. Initial findings indicate that the problem appears to be related to the apitoken / clientApp / accessToken request. More information is available at https://support.onespan.com/csm?id=trust_center_environment_status&environment=baf6c32d1b2be0505ed6fcc2cd4bcb03

3. resolved Jan 10, 2026, 07:45 AM UTC

   The OneSpan issue impacting Sign 2.0 services on Conga Advantage Platform for APAC region has been fully resolved and all affected systems have returned to normal operation.

Read the full incident report →

Started Dec 19, 2025, 11:40 AM UTC· resolved Dec 19, 2025, 08:47 PM UTC

1. investigating Dec 19, 2025, 11:40 AM UTC

   We are currently investigating reports of errors or failures for a few operations when using merge service within U.S region. We will provide further updates as they are available.

2. investigating Dec 19, 2025, 12:50 PM UTC

   Our team is actively working on implementing a fix to resolve the issue. Customers may continue to experience intermittent issues while the solution is being deployed.

3. identified Dec 19, 2025, 02:03 PM UTC

   Our team is actively working to restore our server environments to a stable version of the application. Users may continue to experience intermittent errors while this fix is deployed.

4. identified Dec 19, 2025, 03:40 PM UTC

   We have successfully rebuilt the affected infrastructure and are currently running verification tests to ensure stability. Please note that this issue is primarily impacting RegenerateWithRedlines service with some intermittent failures on Document Merge operations as we work to resolve the issue.

5. identified Dec 19, 2025, 04:40 PM UTC

   Work continues on restoring the service. We are currently finalizing and testing configurations on the rebuilt infrastructure before opening the service to traffic.

6. identified Dec 19, 2025, 05:48 PM UTC

   We have expanded our troubleshooting to include testing of previous application versions, as initial validation checks did not pass. The impact remains to be isolated to RegenerateWithRedline service at this time.

7. monitoring Dec 19, 2025, 07:33 PM UTC

   We have implemented a fix involving increased server capacity to better handle job processing. We're continuing to monitor performance closely to ensure stability.

8. resolved Dec 19, 2025, 08:47 PM UTC

   The issue impacting RegenerateWithRedline Merge service in the NA region has been resolved and all affected systems have returned to normal operation.

Read the full incident report →

Started Nov 18, 2025, 12:13 PM UTC· resolved Nov 18, 2025, 03:26 PM UTC

1. identified Nov 18, 2025, 12:13 PM UTC

   Conga Advantage platform along with other Conga Services are down due to Cloudflare global outage, this issue is impacting all the Conga services in all the regions (North America, EMEA and APAC) (https://www.cloudflarestatus.com/incidents/8gmgl950y3h7) Customers may continue to experience inability to access conga services while the fix is being deployed from cloudflare.

2. identified Nov 18, 2025, 01:45 PM UTC

   Due to the widespread Cloudflare network issues, several of our services have experienced interruptions. We have successfully restored access to the Merge Service and OCC. We are monitoring the situation closely and will continue to provide updates.

3. identified Nov 18, 2025, 01:53 PM UTC

   Our services are currently experiencing intermittent connectivity issues due to the ongoing Cloudflare incident. We are seeing some successful traffic throughput and are monitoring the situation closely as Cloudflare continues their remediation. You may experience occasional timeouts or errors while the global network stabilizes.

4. identified Nov 18, 2025, 02:08 PM UTC

   We have successfully recovered the Conga Contracts service, and it is now fully operational. Our team is currently executing a temporary restoration strategy to bring Turbo Services back online. You may continue to experience intermittent availability with Turbo Services while this process is underway. We remain in a monitoring state as we track the ongoing global Cloudflare outage and will provide further updates as services stabilize. Cloudflare Status: https://www.cloudflarestatus.com/

5. monitoring Nov 18, 2025, 02:57 PM UTC

   Cloudflare has confirmed that a fix has been implemented for the global network issues. We are observing a return to normal operation across all Conga services. We are continuing to monitor while we verify full stability and performance across the platform.

6. resolved Nov 18, 2025, 03:26 PM UTC

   We have confirmed that the upstream Cloudflare network issues are resolved. We have monitored our systems for the last 20 minutes, and all automated tests and health checks are passing.

Read the full incident report →

Started Oct 29, 2025, 04:45 PM UTC· resolved Oct 30, 2025, 12:00 AM UTC

1. investigating Oct 29, 2025, 04:45 PM UTC

   We are currently investigating reports of delays in platform login affecting Conga IDP in all regions. Customers may experience delays in login using Conga IDP and receiving verification codes. This is related to an ongoing Azure service disruption. We will provide further updates as they are available.

2. identified Oct 29, 2025, 05:35 PM UTC

   We’ve identified that the login delays across all RLS environments are caused by an ongoing Azure Front Door (AFD) issue impacting service availability. According to Microsoft, a configuration change triggered the disruption around 16:00 UTC, and they are currently rolling back to a known good state while blocking further changes. Users may continue to experience intermittent login delays until the rollback is complete.

3. identified Oct 29, 2025, 06:38 PM UTC

   Some customers are also reporting slow logins or timeouts in X-Author and X-Author for Contracts. Microsoft incident tracking is reporting fixes are being rolled out with initial recovery already in progress. Microsoft Status Page: https://azure.status.microsoft/en-us/status

4. identified Oct 29, 2025, 07:59 PM UTC

   We are now seeing some internal tests pass with improved latency as Microsoft Azure continues to repair their global service disruption. There is no ETA from Microsoft at this time on full remediation. We are continuing to monitor. Microsoft Status Page: https://azure.status.microsoft/en-us/status

5. identified Oct 29, 2025, 08:50 PM UTC

   Microsoft Azure is reporting a full recovery with an ETA of 4 hours (expected recovery by 23:20 UTC). We are continuing to see improvements with our internal tests, however, customers may still experience latency and timeouts during login until Azure systems have fully recovered. We will continue to monitor the recovery procedures from Microsoft.

6. monitoring Oct 29, 2025, 09:53 PM UTC

   Azure systems are recovering. Conga internal tests are also showing improvement in stability and response times. We'll continue to monitor the recovery procedures. The next update will be in 2 hours or on any major change reported by Microsoft. Microsoft Status Page: https://azure.status.microsoft/en-us/status

7. resolved Oct 30, 2025, 12:00 AM UTC

   Conga Platform and X Author Login services have returned to normal operation following resolution of the Microsoft Azure global service disruption. If you continue to experience any issues, please contact our support team.

Read the full incident report →

Started Oct 28, 2025, 05:39 PM UTC· resolved Oct 28, 2025, 06:49 PM UTC

1. investigating Oct 28, 2025, 05:39 PM UTC

   We are currently investigating reports of increased errors when attempting to create proposals through Conga Collaborate in all regions. Customers may experience inability to create proposals. We will provide further updates as they are available.

2. identified Oct 28, 2025, 06:26 PM UTC

   We've identified the root cause of the issue. Our engineering teams are actively working on implementing a solution to resolve the issue. Customers may continue to experience inability to generate proposals from Salesforce while the fix is being deployed.

3. resolved Oct 28, 2025, 06:49 PM UTC

   The issue impacting Conga Collaborate in all regions has been fully resolved and all affected services have returned to normal operation.

Read the full incident report →

Started Oct 20, 2025, 05:17 PM UTC· resolved Oct 20, 2025, 10:58 PM UTC

1. identified Oct 20, 2025, 05:17 PM UTC

   We have identified a service disruption with our cloud infrastructure provider, Amazon Web Services (AWS), in their NA (us-east-1) region. This is impacting multiple Conga services, and customers may experience increased error rates and latency. Our teams are actively monitoring the provider's status and will post updates here as they become available. AWS Health Dashboard: https://health.console.aws.amazon.com/health/home#/account/dashboard/open-issues

2. identified Oct 20, 2025, 05:50 PM UTC

   We are continuing to monitor the AWS outage status. AWS Health Dashboard: https://health.aws.amazon.com/health/status

3. identified Oct 20, 2025, 06:58 PM UTC

   We are continuing to monitor the ongoing AWS service disruption. While AWS reports that some services are recovering, the impact to Conga products remains limited and intermittent at this time. We will provide another update as more information becomes available. AWS Health Dashboard: https://health.aws.amazon.com/health/status

4. monitoring Oct 20, 2025, 08:35 PM UTC

   We are continuing to monitor the recovery of the AWS outage. AWS is reporting significant progress in restoring services, and we are observing corresponding improvements in our affected products. Some Conga services may still experience intermittent performance issues or errors as the underlying infrastructure fully recovers. Our teams will continue to monitor the situation until all services return to normal operation. AWS Health Dashboard: https://health.aws.amazon.com/health/status

5. resolved Oct 20, 2025, 10:58 PM UTC

   AWS has resolved the service disruption in the NA (US-EAST-1) region. The affected Conga products have returned to normal operation. If you continue to encounter any issues, please contact our support team.

Read the full incident report →

Started Oct 01, 2025, 07:10 PM UTC· resolved Oct 01, 2025, 11:27 PM UTC

1. investigating Oct 01, 2025, 07:10 PM UTC

   We are currently investigating reports of errors or failures when using Smart Search functionality on MAX within the NA and EU regions. Customers may experience inability to use the main search feature. We will provide further updates as they are available.

2. identified Oct 01, 2025, 07:48 PM UTC

   We've identified the root cause of the issue impacting Smart Search functionality. Our engineering teams are actively working on implementing a solution to resolve the issue. Customers may continue to experience errors while the fix is being deployed.

3. identified Oct 01, 2025, 09:01 PM UTC

   Our teams are actively working on a resolution for the ongoing service disruption. Our primary focus is on restoring the service to its last known stable configuration. We expect to confirm the success of this approach within the next hour. We appreciate your continued patience.

4. identified Oct 01, 2025, 10:38 PM UTC

   Our teams are actively engaged in the process of restoring the Smart Search service to a stable and fully functional configuration. Our primary focus is on ensuring the continued stability and integrity of the environment. This is a comprehensive process that our teams are working through with the utmost urgency. We are committed to restoring service as quickly and safely as possible. Smart Search functionality will remain unavailable while this essential work is completed. We will continue to provide updates as progress is made until the service is restored. We appreciate your continued patience and understanding.

5. resolved Oct 01, 2025, 11:27 PM UTC

   The service disruption affecting Conga MAX Smart Search has been fully resolved. All search APIs and related services are now operating normally. The issue was resolved by performing a targeted reset of the affected cache components and re-initializing the service's configuration, which has restored full functionality to the application. Our teams have verified that services are stable and performing as expected. We apologize for the impact this outage has had on your business. Our teams will be conducting a comprehensive post-mortem analysis to understand the full root cause and implement preventative measures to improve the resilience of our services. We thank you for your patience and understanding.

Read the full incident report →

Started Sep 16, 2025, 09:41 PM UTC· resolved Sep 16, 2025, 10:50 PM UTC

1. identified Sep 16, 2025, 09:41 PM UTC

   We are currently investigating reports of intermittent failures affecting Conga Batch and Composer within the EU region. This issue is due to an ongoing Salesforce service disruption affecting customer login capabilities in the region. At this time, there is no impact to Composer API services. Customers may continue to experience intermittent errors as we closely monitor the upstream Salesforce service restoration. Our services will resume normal operations once Salesforce resolves the EU region issues. We will provide further updates as they are available.

2. monitoring Sep 16, 2025, 10:11 PM UTC

   Salesforce has reported all services in the region have been restored. Our systems are recovering, and we are now closely monitoring performance and stability to ensure the issue is fully resolved. Services should now be accessible and functioning normally.

3. resolved Sep 16, 2025, 10:50 PM UTC

   The Salesforce EU region service disruption has been fully resolved. All Conga Batch and Composer services have returned to normal operations. If you're experiencing any issues with batch, please refresh your batch token: https://documentation.conga.com/en/composer-for-salesforce/current/composer-for-administrators/conga-batch/troubleshooting-conga-batch/refreshing-your-salesforce-refresh-token-for-conga-batch If after refreshing, you are still experiencing issues, please open a case with our technical support team in your Conga community portal.

Read the full incident report →

Started Aug 27, 2025, 06:43 PM UTC· resolved Aug 27, 2025, 07:25 PM UTC

1. investigating Aug 27, 2025, 06:43 PM UTC

   We are currently investigating reports of degraded or intermittent services affecting Conga Composer within the NA region. Customers may experience intermittent errors or slow performance on Composer UI. We will provide further updates as they are available.

2. monitoring Aug 27, 2025, 07:42 PM UTC

   A fix has been implemented. Our systems are recovering, and we are now closely monitoring performance and stability to ensure the issue is fully resolved.

3. resolved Aug 28, 2025, 12:05 AM UTC

   The issue impacting Conga Composer UI in the NA region has been fully resolved and all affected systems have returned to normal operation.

4. postmortem Sep 03, 2025, 01:49 AM UTC

   # Composer Service Disruption \(August 26–27, 2025\) ## Summary Between August 26 and 27, 2025, Composer experienced intermittent service degradation for Salesforce users in North America. While some operations continued, many users experienced slow or failed merge operations, significantly impacting productivity. ## Root Cause The disruption was caused by a defect in authentication token validation logic, triggered when new servers with mismatched time zones were introduced. This led to excessive credential validation requests to Salesforce, overwhelming Composer’s infrastructure and causing cascading failures. ## Resolution and Prevention * A permanent fix was deployed on August 28, 2025, resolving the issue * The authentication process was redesigned to prevent similar failures * Monitoring and diagnostic tools were enhanced to detect anomalies earlier * Circuit breakers, load distribution improvements, and Salesforce API usage optimizations have been implemented We recognize the disruption this may have caused to your business and remain committed to providing the best software and experience to our customers. If you have any additional questions, please reach out to the Conga Success Team at [[email protected]](mailto:[email protected]).

Read the full incident report →

Started Jul 04, 2025, 12:29 AM UTC· resolved Jul 04, 2025, 06:38 PM UTC

1. investigating Jul 04, 2025, 12:29 AM UTC

   We are currently investigating reports of issues with generated documents affecting Conga Orchestrate within the NA region. Customers may experience inability to generate documents using Conga Orchestrate. We will provide further updates as they are available.

2. investigating Jul 04, 2025, 01:02 AM UTC

   We are continuing to investigate the issue.

3. investigating Jul 04, 2025, 01:31 AM UTC

   We are continuing to investigate the issue.

4. identified Jul 04, 2025, 02:01 AM UTC

   We've identified the root cause of the issue impacting Conga Orchestrate. Our engineering teams are actively working on implementing a solution to resolve the issue. Customers may continue to experience the inability to generate documents while the fix is being deployed.

5. identified Jul 04, 2025, 02:34 AM UTC

   Our engineering teams are continuing to work on implementing a fix.

6. identified Jul 04, 2025, 03:02 AM UTC

   Our engineering teams are continuing to work on implementing a fix.

7. identified Jul 04, 2025, 03:33 AM UTC

   Our engineering teams are continuing to work on implementing a fix.

8. identified Jul 04, 2025, 04:05 AM UTC

   Our engineering teams are continuing to work on implementing a fix.

9. identified Jul 04, 2025, 04:21 AM UTC

   We are continuing to work on a fix for this issue.

10. identified Jul 04, 2025, 05:17 AM UTC

    Our team is diligently working on implementing a solution.

11. identified Jul 04, 2025, 07:26 AM UTC

    Our team remains committed to prioritising the implementation of a fix.

12. identified Jul 04, 2025, 10:49 AM UTC

    We are continuing to work on a fix for this issue.

13. resolved Jul 04, 2025, 06:38 PM UTC

    Systems have returned to stable operation in the impacted NA region. Some customers may require additional support, and our teams are actively engaged with them. If you continue to see issues with the service, please contact our technical support team.

Read the full incident report →