Conga Contracts 中断历史

1. 2026年8月25日 UTC 13:57investigating

   目前正在调查影响NA区域内平台登录、编译、XA认证的故障问题 客户可能会遇到登录失败的情况. 我们将提供进一步的最新资料.

2. 2026年8月25日 UTC 14:04investigating

   我们正在调查影响NA区域内平台登录、编译、CPQ、CLM、XAuthor的问题。 客户可能会遇到登录失败的情况. 我们将提供进一步的最新资料.

自动翻译自官方事件更新。

1. 2026年8月18日 UTC 11:25investigating

   我们目前正在调查关于Conga平台上影响电子邮件功能的问题的调查报告。 客户可能遇到涉及电子邮件功能的间歇性错误。 我们将提供进一步的最新资料.

2. 2026年8月18日 UTC 12:05monitoring

   已经执行了一项固定措施。 我们的系统正在恢复,我们现在正在密切监测业绩和稳定性,以确保这一问题得到全面解决。 Conga平台上的电子邮件功能现在应该可以访问并正常运行.

3. 2026年8月18日 UTC 12:53resolved

   影响电子邮件功能的问题已完全解决,所有受影响的系统已恢复正常运行.

自动翻译自官方事件更新。

1. 2026年7月28日 UTC 20:24investigating

   我们目前正在调查有关北美地区Conga合同业绩退化的报告。 客户可能会出现间歇性出错并缓慢表现. 我们将提供进一步的最新资料.

2. 2026年7月28日 UTC 23:30investigating

   我们正在继续调查这一问题.

3. 2026年7月29日 UTC 00:33identified

   我们查明了造成业绩问题的资源限制。 为了处理这些调查结果,我们正在采取更多的改进措施,作为即将发布的部分内容。 我们的小组仍然积极参与环境监测并努力改进业绩和稳定。 这仍然是我们小组的最高优先事项,我们将继续在获得更多信息后提供最新情况.

4. 2026年7月29日 UTC 06:29identified

   我们的小组继续积极努力解决已查明的资源限制,并改进工作,以加强业绩和稳定。 在进行这些努力的同时,环境仍然受到密切监测。 这仍然是一个最优先事项,我们将随着进展提供进一步的最新情况.

5. 2026年7月29日 UTC 14:41identified

   我们的团队正在解决资源制约和改善总体业绩方面取得稳步进展。 我们继续密切监测环境,而其余的改进工作则在进行之中。 随着工作的进行,我们将进一步介绍最新情况.

6. 2026年7月29日 UTC 19:24monitoring

   已经执行了一项固定措施。 我们的系统正在恢复,我们现在正在密切监测业绩和稳定性,以确保这一问题得到全面解决。 服务现在应当能够利用并正常运作.

7. 2026年7月29日 UTC 20:48monitoring

   我们的系统继续恢复。 我们正看到业绩和稳定性的全面改善,大多数客户都应获得并正常运作服务。 虽然情况有所改善,但有些客户可能仍会遇到断断续续的问题。 我们的小组正在继续密切监测系统的业绩和稳定性,并正积极努力处理所余影响。 这仍然是我们小组的最高优先事项,我们将继续在获得更多信息后提供最新情况.

8. 2026年7月30日 UTC 00:32monitoring

   我们继续监测系统的业绩和稳定性,并看到持续改善。 一些客户可能仍会遇到断断续续的问题,我们的工程团队仍然积极参与环境监测并处理所余影响. 我们将继续在获得更多信息后提供最新情况.

9. 2026年8月6日 UTC 07:06resolved

   The issue impacting Conga Contracts in the NA region has been fully resolved and system has been operating normally for the past 2 days. We appreciate your patience and understanding while we worked to resolve this issue.

自动翻译自官方事件更新。

1. 2026年7月23日 UTC 16:48investigating

   目前,我们正在调查一个影响以Conga境内流离失所者为登录方法的客户认证的问题。 目前,影响仅限于Conga国内流离失所者认证。 其他得到支持的认证方法仍在运作。 我们的工程团队正在积极监测美国西部地区正在发生的Azure服务问题,这个问题可能会助长这种行为,并正在努力尽量减少对客户的影响。 我们将继续在获得更多信息后提供最新情况。 微软Azure现状:https://azure.status.microsoft/en-us/status

2. 2026年7月23日 UTC 18:13identified

   我们继续监测正在发生的影响到美国西部地区的Azure服务事件。 影响仍限于使用Conga境内流离失所者作为认证方法的客户。 其他支持的登录方法继续正常运行. 微软已查明Azure服务中断的可能原因并正在积极部署缓解行动。 我们正同阿祖尔一起密切监测恢复情况,并将继续随着服务恢复的进展提供最新情况。 微软Azure现状:https://azure.status.microsoft/en-us/status

3. 2026年7月23日 UTC 20:44resolved

   影响康加境内流离失所者认证的问题已经得到解决。 微软已完成了对影响美国西部地区的Azure服务中断的缓解,我们的监测表明Conga国内流离失所者认证已经恢复正常运行.

自动翻译自官方事件更新。

1. 2026年7月21日 UTC 17:38investigating

   我们目前正在调查对北美地区康加合同影响的持续业绩退化。 我们的工程团队正积极开展工作,找出根源,并落实缓解措施,以尽快恢复正常的服务水平. 在此期间,客户在使用Conga Contracts时可能会遇到比正常的反应时间更慢和间歇性延误. 我们将继续在获得更多信息后提供最新情况。 需要实时更新,请监控我们的状态页面:status.conga.com

2. 2026年7月22日 UTC 07:14resolved

   影响北美地区康加合同的问题已完全解决,过去9小时,该系统一直正常运行.

自动翻译自官方事件更新。

1. 2026年7月20日 UTC 15:29investigating

   我们目前正在调查有关在北美地区影响康加合同的服务影响的报告。 客户在尝试登录时可能遇到间歇性错误. 我们将提供进一步的最新资料.

2. 2026年7月20日 UTC 16:29investigating

   我们继续调查影响北美地区康加合同的服务影响。 客户可能继续发生间歇性错误。 一旦获得更多信息,我们将提供下一次最新情况.

3. 2026年7月20日 UTC 18:21identified

   我们查明了根源,我们的工程团队正在积极实施解决问题的办法. 在安装固定装置时,客户可能继续发生间歇性错误和性能下降.

4. 2026年7月20日 UTC 19:43identified

   我们的工程小组正在积极调查这一问题的根源,并正努力尽快执行一项决议。 在这项工作进行期间,一些客户可能继续发生间歇性错误或业绩退化。 我们将继续在获得更多信息后提供最新情况.

5. 2026年7月20日 UTC 20:13monitoring

   已经执行了一项固定措施。 我们的系统正在恢复,我们现在正在密切监测业绩和稳定性,以确保这一问题得到全面解决。 服务现在应当能够利用并正常运作.

6. 2026年7月20日 UTC 21:02resolved

   影响北美地区康加合同的问题已完全解决,所有受影响的系统已恢复正常运行.

自动翻译自官方事件更新。

1. 2026年7月15日 UTC 23:26investigating

   我们正在调查欧盟地区涡轮生产租户的一问题。 客户可能会遭遇间歇性服务中断和应用程序性能下降. 一旦获得进一步的最新资料,我们将予以提供.

2. 2026年7月15日 UTC 23:36monitoring

   我们的系统正在恢复,我们现在正在密切监测业绩和稳定性,以确保这一问题得到全面解决。 用户应当看到性能恢复正常.

3. 2026年7月15日 UTC 23:48resolved

   影响欧盟区域涡轮产品的问题已完全解决,所有受影响的系统已恢复正常运行.

自动翻译自官方事件更新。

1. 2026年7月15日 UTC 18:22investigating

   我们目前正在调查有关在北美地区影响康加合同的服务影响的报告。 客户在尝试登录时可能遇到间歇性错误. 我们将提供进一步的最新资料.

2. 2026年7月15日 UTC 18:50monitoring

   已经执行了一项固定措施。 我们的系统正在恢复,我们现在正在密切监测业绩和稳定性,以确保这一问题得到全面解决。 服务现在应当能够利用并正常运作.

3. 2026年7月15日 UTC 19:47resolved

   影响北美地区康加合同的问题已完全解决,所有受影响的系统已恢复正常运行.

自动翻译自官方事件更新。

1. 2026年7月15日 UTC 15:51investigating

   我们目前正在调查有关在北美地区影响康加合同的服务影响的报告。 客户在尝试登录时可能遇到间歇性错误. 我们将提供进一步的最新资料.

2. 2026年7月15日 UTC 16:39monitoring

   已经执行了一项固定措施。 我们的系统正在恢复,我们现在正在密切监测业绩和稳定性,以确保这一问题得到全面解决。 服务现在应当能够利用并正常运作.

3. 2026年7月15日 UTC 16:49resolved

   影响北美地区康加合同的问题已完全解决,所有受影响的系统已恢复正常运行.

自动翻译自官方事件更新。

1. 2026年6月29日 UTC 02:55monitoring

   Following the Composer Conga Platform 202606.1.0 release, solutions leveraging the Field Data Source parameter are failing to merge intermittently. If encountered, customers leveraging the Field Data Source parameter must add the &platformcomposer=1 parameter to their existing Composer solution. Without this change, Composer merges leveraging the Field Data Source parameter could fail. The root cause is still under investigation. Once identified, a fix will be automatically deployed. Who is affected: Composer customers leveraging the Field Data Source parameter. Required action: A Salesforce System Administrator must complete the following steps. Step 1: Identify any Composer solution(s) that include the Field Data Source parameter. Step 2: Add the &platformcomposer=1 parameter to all Composer solutions that currently include the Field Data Source parameter. Contact Conga Support if issues persist after completing these steps.

2. 2026年6月29日 UTC 22:55resolved

   This incident has been resolved.

1. 2026年6月18日 UTC 10:43investigating

   We are currently investigating reports of gateway time out errors affecting Conga Contracts. Customers may experience intermittent errors. We will provide further updates as they are available.

2. 2026年6月18日 UTC 11:44investigating

   We continue to actively investigate the gateway timeout errors affecting the Conga Contracts product. Customers may continue to experience intermittent errors and degraded performance while remediation efforts are underway. We will provide the next update as soon as more information becomes available.

3. 2026年6月18日 UTC 13:05investigating

   We continue to actively investigate the gateway timeout errors affecting the Conga Contracts. Our engineering teams are engaged and analyzing the underlying cause. Customers may continue to experience intermittent errors and degraded performance while the investigation remains ongoing. We appreciate your patience and will provide additional updates as soon as more information becomes available.

4. 2026年6月18日 UTC 14:39monitoring

   A fix has been implemented to address the issue, and our internal validations have completed successfully. Our teams are actively monitoring the system to ensure ongoing stability.

5. 2026年6月18日 UTC 14:56resolved

   The issue impacting Composer has been fully resolved and all affected systems have returned to normal operation. We appreciate your patience and understanding while we worked to resolve this issue.

1. 2026年5月21日 UTC 22:03investigating

   Salesforce Core services are currently experiencing performance degradation, which is intermittently impacting Turbo SFDC authentication. This includes things like: Authentication and login services API endpoints Database/platform infrastructure CRM application backend services Metadata and workflow services We are closely monitoring the Salesforce outage and will provide updates as we learn more.

2. 2026年5月21日 UTC 23:24investigating

   Salesforce is still continuing to investigate the issue.

3. 2026年5月22日 UTC 00:23monitoring

   Salesforce has done rolling restarts, released connections with pre-mitigation configurations, and currently performing final validations and taking proactive actions to ensure full remediation. With the Salesforce rolling restarts, all Conga Turbo services are operation, but we are monitoring the situation actively until Salesforce outrage is fully resolved.

4. 2026年5月22日 UTC 04:36resolved

   This incident has been resolved.

1. 2026年5月21日 UTC 15:05investigating

   We are currently investigating this issue.

2. 2026年5月21日 UTC 18:44investigating

   The fix did not work, we are still facing 504 issues. We are investigating it.

3. 2026年5月21日 UTC 21:06investigating

   We've scaled up our infrastructure and seen performance improvements, but are still addressing intermittent timeouts being observed by some customers. We will provide further updates as they are available.

4. 2026年5月21日 UTC 22:25investigating

   We are continuing to investigate a root cause while scaling infrastructure to help improve performance and stability.

5. 2026年5月21日 UTC 22:52identified

   The issue has been identified and a fix is being implemented.

6. 2026年5月21日 UTC 22:55monitoring

   A fix has been implemented and we are monitoring the results.

7. 2026年5月21日 UTC 23:11resolved

   The issue has been fully resolved and all affected systems have returned to normal operation.

1. 2026年5月14日 UTC 20:15investigating

   We are currently investigating reports of service impact affecting Conga Sign Professional within the NA region. Customers may experience inability to resend transactions and the View Audit button not re-directing properly. We will provide further updates as they are available.

2. 2026年5月14日 UTC 21:20resolved

   After investigation, this is not a service-wide incident. The issues with resending transactions and the View Audit button have been confirmed as an intermittent product defect and are being addressed by Engineering as a high priority item. Affected customers should contact Conga Support for updates.

1. 2026年5月11日 UTC 11:03investigating

   We are aware of an issue impacting Conga Contracts for Salesforce, imacting all regions and team is working towards implementing a fix. Users may get errors while editing the Contract record (SalesForce standard contract object). We will provide further updates as they are available.

2. 2026年5月11日 UTC 12:53investigating

   We continue to investigate the issue impacting Conga Contracts for Salesforce across all regions. Users may continue to experience errors while editing Contract records within the Salesforce standard Contract object. Our engineering teams are actively analyzing the issue and working towards implementing a fix to restore normal functionality. We appreciate your continued patience and will provide further updates as more information becomes available.

3. 2026年5月11日 UTC 15:17identified

   We've identified the root cause of the issue impacting Conga Contracts for Salesforce. Our engineering teams are actively working on implementing a solution to resolve the issue. Customers may continue to experience failure while editing Contract records within the Salesforce standard Contract object / files, while the fix is being deployed.

4. 2026年5月11日 UTC 16:48identified

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

5. 2026年5月11日 UTC 18:45identified

   Our engineering team has prepared a targeted fix and is currently validating the update prior to deployment. We will continue to provide updates as implementation progresses.

6. 2026年5月11日 UTC 21:31identified

   Deployment of the targeted fix is currently in progress. Our teams are actively monitoring the rollout and validation activities, and we will continue to provide updates as progress continues.

7. 2026年5月11日 UTC 23:08identified

   Deployment of the targeted fix is continuing to progress.

8. 2026年5月12日 UTC 06:43identified

   During validation, the previously identified fix did not fully resolve the issue as expected. Teams are continuing deeper analysis and working on an updated remediation approach to restore normal functionality. We will continue to provide timely updates as progress is made.

9. 2026年5月12日 UTC 09:30identified

   Our engineering teams have developed an updated fix for the issue and are currently validating the solution prior to rolling it out. We are closely monitoring the validation process and will provide further updates as progress continues.

10. 2026年5月12日 UTC 09:46identified

    Our engineering teams have successfully validated the updated fix for the issue impacting Conga Contracts for Salesforce and have begun deploying the remediation. Users may continue to experience errors while the rollout is in progress. We are actively monitoring the deployment and will provide further updates once implementation has been fully completed.

11. 2026年5月12日 UTC 12:53monitoring

    The fix for the issue has been successfully deployed across the regions, and our team is actively monitoring the environment to ensure stability and full recovery.

12. 2026年5月12日 UTC 13:55resolved

    The issue impacting Conga Contracts for Salesfroce in the all regions has been fully resolved and all affected systems have returned to normal operation.

1. 2026年5月9日 UTC 13:59resolved

   Hello Conga Sign Customer, We are writing to inform you that some customers may experience issues with sending transactions or synchronization in Conga Sign Professional following our release maintenance today. If you are impacted, please reconnect your OAuth connection by following these steps: Salesforce Org → Conga Sign Setup → Org Configuration → Connect with OAuth → Reconnect Thank you, Conga Team

1. 2026年4月20日 UTC 05:55investigating

   We are currently investigating reports of service degradation affecting Composer in all regions. Customers may be unable to create Salesforce tasks or activities due to insufficient permissions at the moment. We will provide further updates as they are available.

2. 2026年4月20日 UTC 06:57identified

   We've identified the root cause of the issue impacting Conga composer. Our engineering teams are actively working on implementing a solution to resolve the issue. Customers may continue to experience failure around create Salesforce tasks or activities operations while the fix is being deployed.

3. 2026年4月20日 UTC 07:59identified

   Our engineering teams are continuing to implement the fix. The issue remains under active investigation and has not yet been fully resolved. Customers may continue to experience failures when creating Salesforce tasks or activities operations while remediation efforts are ongoing. We will provide the next update as soon as additional information becomes available.

4. 2026年4月20日 UTC 08:57identified

   The Conga team is continue to actively work on implementing the fix and remediation efforts are still in progress. We are closely monitoring the progress and will provide further updates as soon as more information becomes available. Thank you for your continued patience and understanding.

5. 2026年4月20日 UTC 10:16monitoring

   A fix has been implemented to address the issue, and our internal validations have completed successfully. Our teams are actively monitoring the system to ensure ongoing stability.

6. 2026年4月20日 UTC 11:24resolved

   The issue impacting Composer has been fully resolved and all affected systems have returned to normal operation. We appreciate your patience and understanding while we worked to resolve this issue.

1. 2026年4月2日 UTC 16:21investigating

   We are aware of an issue impacting Conga Contracts affecting Conga Contracts within the NA region. Customers may experience intermittent errors or an inability to access the application. We will provide further updates as they are available.

2. 2026年4月2日 UTC 16:57monitoring

   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. 2026年4月2日 UTC 17:19resolved

   The issue impacting Conga Contracts in the NA region has been fully resolved and all affected systems have returned to normal operation. Customers who are still experiencing issues may need to log out of their SSO account and log back in.

1. 2026年3月21日 UTC 01:36investigating

   We are currently investigating the issue

2. 2026年3月21日 UTC 01:59identified

   The issue has been identified and a fix is being implemented.

3. 2026年3月21日 UTC 02:55monitoring

   A fix has been implemented and we are monitoring the results.

4. 2026年3月21日 UTC 03:31resolved

   This incident has been resolved.

1. 2026年3月19日 UTC 20:49investigating

   We are currently investigating this issue.

2. 2026年3月19日 UTC 21:01identified

   The issue has been identified and a fix is being implemented.

3. 2026年3月19日 UTC 21:31monitoring

   A fix has been implemented and we are monitoring the results.

4. 2026年3月19日 UTC 22:07resolved

   This incident has been resolved.