Copado 中断历史

1. 2026年9月16日 UTC 08:47identified

   问题摘要: 销售力量正式承认,全球服务持续中断,影响到其核心服务。 这种基础设施的断电是目前影响我们环境的间歇性维修错误和出入问题的根源。 当前状况 : 事件编号:https://status.salesforce.com/incidents/20004433 根源:全球销售力量核心服务中断。 下一步动作( A) : Track Re-Term Re-Time Updates:请监控官方的"销售力量信托"链接,以便直接从"销售力量"工程获得更新. 支持入场券请求:我们恳请各位继续避免打开科帕多支持或IT入场券, 我们正在密切监测销售力量的进展,并将在平台功能稳定后立即发布另一次更新.

2. 2026年9月16日 UTC 12:19monitoring

   当前状况 销售部队在基础设施中安装了固定装置,在受影响的情况下,服务正在积极恢复正常。 随着平台性能稳定,我们的团队将状态更新至"监测". 事件进展 服务恢复:销售部队正在全机推出,系统可用性正在恢复。 永久决议: 在推出的同时,工程组正在执行一个永久性的代号级固定措施来防止再次发生. 内部监测:我们正在积极监测出错率和遥测情况,以核实是否完全稳定。 客户指导 大多数用户现在应该能够查阅他们的Copado实例和Copado社区,而不会遇到维护错误。 如果您遇到任何剩余时间或短暂打嗝, 请稍候, 并刷新您的浏览器会话 .

3. 2026年9月16日 UTC 18:03resolved

   这一事件已经得到解决.

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

1. 2026年8月27日 UTC 08:46investigating

   我们目前正在调查少数客户关于意外执行职务的报告。 我们的团队正在积极检讨行为,并努力更好地理解这个问题. 在我们目前正在调查这个问题时,如果你遇到任何相关问题,请通过我们的成功共同体来立案.

2. 2026年8月27日 UTC 12:25investigating

   我们仍然在积极调查这一问题并努力寻求解决办法。 我们将在获得更多信息后更新这一状况.

3. 2026年8月28日 UTC 06:12monitoring

   我们不再收到意外工作被处决的报告。 我们正在同销售部队合作,以确定根源,并将继续监测任何再次发生的情况.

4. 2026年8月28日 UTC 07:21resolved

   我们确认,这个问题的根源是众所周知的销售力量产品缺陷。 Salesforce正在积极制定固定办法,目前正在计划将其作为《早期发布》提供。 详情请参见:https://help.salesforce.com/s/issue?id=a02g7007hHG5AAM. 我们正在将这一事件定为已解决.

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

1. 2026年8月21日 UTC 18:24investigating

   我们目前正在跟踪影响Org认证和Copado部署的销售力量服务退化情况。 我们正密切监测局势,并将在掌握最新情况后提供进一步的最新资料。 请检查access-date=中的日期值 (帮助) Salesforce.com 了解更多详情.

2. 2026年8月21日 UTC 21:57monitoring

   销售力的退化使得活性刷新托肯斯失效,使科帕多工作失去连接到它们所连接的兽群的准入. 要恢复功能,请执行以下步骤: 1. 重新认证您的 Copado 用户证书以生成新的、有效的刷新令牌。 2. 重试任何失败的 Copado 工作 。 如果你在重新认证后继续遇到任何问题,请联系我们的支援小组寻求援助.

3. 2026年8月22日 UTC 02:16resolved

   我们确定,在最后一小时没有发生更多事件。 这一事件已经得到解决.

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

1. 2026年7月21日 UTC 09:58investigating

   我们目前正在调查一个影响到一些客户的问题,这些客户在实施或推广部件时遇到Git认证错误。 我们的工程团队正积极开展工作,找出根源,尽快恢复正常功能. 我们将继续在获得更多信息后提供最新情况.

2. 2026年7月21日 UTC 10:46identified

   我们确认,影响客户的Git认证错误与正在进行的GitHub服务事件有关:https://www.githubstatus.com/ 我们正在密切监测,并将在获得更多信息后更新这一状况.

3. 2026年7月21日 UTC 12:09monitoring

   GitHub的地位已经更新,以表示事件已经解决. 一旦确认恢复了全部功能,我们将监测并更新这一事件,以便解决.

4. 2026年7月21日 UTC 13:11resolved

   我们确定,在最后一小时没有发生更多事件。 这一事件已经得到解决.

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

1. 2026年7月15日 UTC 21:25investigating

   我们从少数客户那里收到报告,这些客户在使用CCD管道时遇到与储存库有关的问题。 由于这些报告的模式,我们目前正在调查这一潜在的服务退化。 虽然你们的具体兽群和CIDC行动不会受到影响.

2. 2026年7月15日 UTC 23:34resolved

   这已经解决了.

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

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

   我们正在调查涉及元数据格式管道的影响到晋升问题的报告。 我们的工程组正在积极调查,并将在获得更多信息后提供最新情况。 我们的下一次更新将在一小时内完成.

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

1. 2026年5月11日 UTC 15:23investigating

   We are currently investigating reports of performance degradation impacting CI/CD pipelines. During this time, some users may also experience intermittent delays or unexpected validation errors when utilizing the CICD Pipeline, which may also affect the Data Deploy Service. Our engineering teams are actively looking into the situation to identify the root cause. We will provide an update as soon as more information is available.

2. 2026年5月11日 UTC 15:44investigating

   The majority of the instability being experienced is due to the "frequent rotation of Refresh Tokens" now being enforced by Salesforce, which we are in the process of further mitigating, at scale.

3. 2026年5月11日 UTC 19:05monitoring

   Status update: Monitoring We have observed a complete drop in authentication errors over the last hour and currently consider this issue resolved. Our team will continue to monitor the system to ensure stability. Action required: If you experienced an error, please re-authenticate your credentials and retry your jobs. Please note that the main Credential for the Org where Copado is installed must be validated first; after that is complete, all subsequent Credential records must be validated by their respective record owners in Salesforce.

4. 2026年5月11日 UTC 20:21resolved

   We have implemented the necessary backend mitigations to resolve the recent service disruptions, and system stability has been fully restored. Action required: If you experienced an error, please re-authenticate your credentials and retry your jobs. Please note that the main Credential for the Org where Copado is installed must be validated first; after that is complete, all subsequent Credential records must be validated by their respective record owners in Salesforce.

1. 2026年5月5日 UTC 14:58investigating

   We are currently investigating an issue affecting Copado AI Services, where users may be experiencing consistent "Agentic LLM task failed" errors. Our engineering team has identified that this is stemming from an overloaded state with one of our upstream AI providers (Anthropic) in our primary hosting region, North America. We are treating this with the highest priority and will provide another update as soon as we have more information or a resolution.

2. 2026年5月5日 UTC 15:59investigating

   We are continuing to investigate this issue.

3. 2026年5月5日 UTC 16:00monitoring

   We have successfully resolved the issue affecting Copado AI Services for our North American servers. Normal service has been fully restored, and users should no longer experience errors when utilizing AI features. We will continue to monitor the service closely to ensure optimal performance. We apologize for any inconvenience this caused and appreciate your patience while our team worked to restore service.

4. 2026年5月5日 UTC 20:07resolved

   Update - Resolved Our monitoring period has concluded, and we have confirmed that Copado AI Services are fully operational and performing as expected for all North American servers. This incident is now resolved. Thank you for your patience.

1. 2025年10月20日 UTC 15:45monitoring

   We are currently experiencing a partial outage due to an ongoing issue with Amazon Web Services (AWS), primarily affecting the US-EAST-1 region. This issue has also impacted certain Salesforce-hosted environments, including our US CRT/AI infrastructure. While AWS initially began showing signs of recovery around 5:10 AM PDT, subsequent challenges in their mitigation efforts have resulted in renewed instability. As of now, both AWS and Salesforce continue to report this as an active incident. Due to the dependencies between our systems and these third-party services, a growing number of customers are experiencing service disruptions or inaccessibility across multiple products — including CRT, AI, CI/CD, and Essentials. Our engineering team is actively engaged and continuing to monitor the situation closely. We are working with our partners at AWS and Salesforce to restore full service as quickly as possible. Next update: As soon as new information becomes available.

2. 2025年10月20日 UTC 16:40monitoring

   We are currently seeing a broader impact across US services. Live Testing in CRT US is likely heavily impacted, and we are also receiving reports of document upload failures in AI for US-based users. Our team is actively monitoring and working with AWS and Salesforce to mitigate the issue. Next update: As soon as new information becomes available.

3. 2025年10月20日 UTC 21:10monitoring

   We have seen improvements in the availability and performances of our services, as well as reduced errors connecting to Salesforce. This has been further confirmed by updates from AWS and Salesforce, respectively. We are continuing to monitor the situation and will post further updates, but we believe things are trending positively. Next update: As soon as new information becomes available.

4. 2025年10月20日 UTC 23:32identified

   We have continued to monitor this situation and mostly positive improvements across our products and connectivity with Salesforce. At approximately 23:00 UTC, AWS marked their ongoing incident as resolved. Salesforce continues to consider this incident ongoing, however we are updating our status to reflect the resolution on the AWS side, and now consider this incident to only be degraded performance rather than a partial outage. Customers may still experience issues with any operations that connect to Salesforce.

5. 2025年10月21日 UTC 01:06resolved

   Salesforce has updated their status at 00:30 UTC and marked this incident as resolved. We now also will mark this incident as resolved.

1. 2025年8月18日 UTC 16:32identified

   An issue related to projects in Copado Robotic Testing has been identified affecting multiple customers in different regions. Our team is investigating the cause of the error and will provide updates as quickly as possible. We apologize for the inconvenience.

2. 2025年8月18日 UTC 19:03resolved

   All regions are operational again. This incident has been resolved.

1. 2025年6月12日 UTC 18:53investigating

   We have detected a global service disruption as of 13:28 CST, which is impacting, but is not limited to, both Google Cloud and Amazon Web Services worldwide. This disruption is impacting Copado, Salesforce, and many other products and services. During this time you may experience issues such as inability to login, authenticate, and interact with Copado/Salesforce. We will continue to update our status as more information becomes available.

2. 2025年6月12日 UTC 19:24investigating

   We are seeing a partial recovery in internal Copado Job executions. All the systems have been updated to Degraded Performance.

3. 2025年6月12日 UTC 20:08monitoring

   We have observed a full recovery across Copado Robotic Testing, Copado Explorer, Essentials, and Copado AI services. We are still seeing partial degradation affecting CICD jobs. Our team is actively monitoring the situation to ensure full restoration of all services.

4. 2025年6月12日 UTC 20:55resolved

   Google Cloud's mitigation efforts have led to all services showing significant recovery. We will continue to monitor to ensure we don't see signs of the disruption recurring, but at this time, all known impact has subsided. All services are operational.

1. 2025年3月3日 UTC 22:35identified

   It appears that Salesforce has introduced a change to the Partner WSDL in patch 9.9 which is unexpectedly returning JSON for the certain objects in the describe call. This is affecting customers on this version in their ability to get metadata, and to create snapshots. We have temporarily implemented a method to ignore this object in the Salesforce Partner WSDL and have informed Salesforce of the issue. Our engineering and infrastructure teams are engaged and we will share updates here as our investigation continues.

2. 2025年3月4日 UTC 13:34identified

   Our engineering team has reviewed this issue further, and confirmed that customers on Salesforce patch 9.10 are also affected, due to another object not included in the library. They have prepared a hotfix which addresses all cases. This hotfix is being tested now and will be released shortly.

3. 2025年3月4日 UTC 15:06monitoring

   The hotfix has been released. We will monitor the impact for a short period and update this incident to Resolved.

4. 2025年3月4日 UTC 16:40resolved

   After the hotfix, our monitoring shows no new instances of this error occurring- this incident is being marked Resolved.

1. 2024年11月27日 UTC 23:06resolved

   On 11/18/2024, at 4:00 AM UTC, customers on our APAC backend experienced interruptions resulting job delays and errors during their use of Copado. Our engineering team investigated and identified issues related to the latest backend release. The team implemented the necessary changes on 11/18/2024 at 8:20 AM UTC, and service resumed to normal. We apologize for any inconvenience.

1. 2024年7月18日 UTC 10:23investigating

   The Copado Success community is currently inaccessible for some users, or loading but with some functionality unavailable. We are currently engaged with Salesforce support to resolve the issue.

2. 2024年7月18日 UTC 15:01resolved

   This incident has been resolved.

1. 2024年7月18日 UTC 01:50investigating

   The Copado Success community is currently inaccessible for some users, or loading but with some functionality unavailable. We are currently engaged with Salesforce support to resolve the issue.

2. 2024年7月18日 UTC 02:38resolved

   This issue is now resolved.

1. 2024年6月28日 UTC 18:49investigating

   We are investigating an issue reported by multiple customers related to GitHub pull requests. At this point, we believe this issue is caused by GitHub's ongoing incident, as indicated on https://www.githubstatus.com/. No changes have been made to Copado's backend or infrastructure that coincide with this issue. We will update as more information becomes available

2. 2024年6月29日 UTC 01:44investigating

   While GitHub is reporting their incident as resolved, we still have customers experiencing issues. We will continue to investigate.

3. 2024年7月1日 UTC 14:19resolved

   Our team has identified the issue, and implemented the necessary changes.

1. 2024年4月24日 UTC 13:13identified

   Copado has identified that Azure DevOps Saas began experiencing service degradation and availability issues starting at approximately 2:30 PM Central Time on April 23, 2024, that could result in failed authentication to Azure DevOps repos via HTTPS. We are currently working with our engineering and infrastructure teams to help identify impacted customers, and are monitoring the ADO status via their site, https://status.dev.azure.com. We have confirmed that this problem does not impact customers utilizing SSH to connect to their repositories. We currently recommend that if possible, customers update their Git Repository record configuration from HTTPS to SSH, to mitigate this outage and return to the full use of Copado and their pipelines with ADO Saas repositories. If you need assistance with this change, please reach out to Copado Support via https://success.copado.com. We will provide updates as more information becomes available.

2. 2024年4月24日 UTC 14:38identified

   We have updated this incident to indicate broader impact; we are seeing examples of customers using Azure DevOps that are experiencing issues beyond authentication. ADO has also broadened the impact of their ongoing incident: https://status.dev.azure.com/_event/496920595 We recommend contacting ADO directly if you are utilizing an ADO repository and are experiencing issues, including but not limited to authentication, performance, and availability.

3. 2024年4月24日 UTC 18:11identified

   We are actively engaged with ADO support and they have provided an estimate of 4 hours to complete the work required to resolve this issue.

4. 2024年4月25日 UTC 02:53resolved

   This incident has been resolved.

1. 2024年1月23日 UTC 17:55identified

   We have identified multiple jobs, across various customers, which are being impacted by delays in metadata retrieval from Salesforce. While this apparent performance degradation is currently not listed on status.salesforce.com, we have engaged Salesforce directly for further clarity. In our initial testing, it appears the impact is limited to Hyperforce instances. In the majority of cases, this issue simply impacts the duration of the associated job. In limited examples we have seen jobs fail due to timeouts as a result of this delayed response. We will update this incident as more information is available.

2. 2024年1月23日 UTC 21:11identified

   We are still awaiting a response from the Salesforce team; we continue to see job performance impacted by delays in metadata retrieval.

3. 2024年1月24日 UTC 01:47resolved

   We are no longer seeing impacted jobs. This issue appears to have been related to Incident ID 12223 (https://status.salesforce.com/incidents/12223). We are working with Salesforce to confirm.

1. 2023年11月2日 UTC 15:06identified

   We are tracking two separate Salesforce incidents that are impacting our customers’ use of Copado: Record relationship Feature Degradation (Global Issue): https://status.salesforce.com/generalmessages/1220 Instance Outage (Regional Issue) https://status.salesforce.com/incidents/11897 While there is no impact to the Copado Infrastructure itself, we have seen examples where the Salesforce records associated with Copado jobs are not successfully created. We recommend delaying any Copado actions until Salesforce has confirmed these incidents are resolved. We also recommend that our customers review any jobs that were already performed during the incidents to confirm the records were created successfully. Additionally, these incidents are impacting our own Salesforce instance. Support for any cases submitted while the incidents are ongoing may be delayed, and there is a possibility that any cases created during the incidents, or during the mitigation actions that are occurring now, may not have been successfully transmitted. Please follow up to confirm successful transmission of support cases after the Salesforce issues are resolved.

2. 2023年11月2日 UTC 15:29identified

   Salesforce has indicated that one of the two incidents (below) is resolved; however, we still recommend delaying any activities within Copado until the other incident is resolved. Instance Outage (Regional Issue) - Now Resolved https://status.salesforce.com/incidents/11897

3. 2023年11月2日 UTC 18:44identified

   Salesforce is performing a rollback of the latest release to resolve the remaining incident. Initial testing suggests that this is resolving previously reported issues. We will continue to monitor and update this status to resolved once Salesforce indicates the rollback is complete.

4. 2023年11月3日 UTC 15:47resolved

   Salesforce has indicated that the second incident impacting the use of Copado is now resolved. We are marking this as resolved, but will continue to monitor for impact from both of the reported incidents.

1. 2023年10月16日 UTC 21:39investigating

   When committing to version control on any job in Copado Essentials Plus via Deployment, Work Item or CI job will result in error "Error: An error occurred while processing your request. Please contact our customer support if the error persists.". We are aware of the issue and working diligently to resolve the matter as quickly as possible. Work Around: no current work arounds are available.

2. 2023年10月17日 UTC 00:47identified

   Copado Essentials Engineering and Copado Infrastructure Engineering have tentatively identified the issue and have run a number of successful Git deployments. We will provide another update shortly with more details.

3. 2023年10月17日 UTC 00:52monitoring

   We have implemented a fix and the issue with deploying to Git repos has been tentatively resolved. We will continue to update you here. Our Apologies for this inconvenience.

4. 2023年10月17日 UTC 02:00resolved

   This incident has been resolved.