Historial de interrupciones de Copado

1. August 27, 2026 at 8:46 AM UTCinvestigating

   Actualmente estamos investigando informes de un pequeño número de clientes sobre ejecuciones de trabajo inesperadas. Nuestro equipo está revisando activamente el comportamiento y trabajando para comprender mejor el problema. Mientras estamos investigando esto, por favor no dude en abrir un caso a través de nuestra comunidad de éxito si usted está experimentando problemas relacionados.

2. August 27, 2026 at 12:25 PM UTCinvestigating

   Todavía estamos investigando activamente esta cuestión y trabajando para lograr una resolución. Actualizaremos este estado con más información mientras esté disponible.

3. August 28, 2026 at 6:12 AM UTCmonitoring

   Ya no estamos recibiendo informes de ejecuciones de trabajo inesperadas. Trabajamos con Salesforce para determinar la causa raíz y seguiremos monitoreando para cualquier recurrencia.

4. August 28, 2026 at 7:21 AM UTCresolved

   Hemos confirmado que la causa raíz de este problema es un error de producto conocido de Salesforce. Salesforce está trabajando activamente en una solución y actualmente está planeando ponerla a disposición como un lanzamiento temprano. Los detalles pueden encontrarse aquí: https://help.salesforce.com/s/issue?id=a02g7000007hHG5AAM Estamos marcando este incidente como resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 21, 2026 at 6:24 PM UTCinvestigating

   Actualmente estamos rastreando la degradación de los servicios de Salesforce impactando la autenticación de org y las implementaciones de Copado. Estamos monitoreando la situación de cerca y proporcionaremos más actualizaciones a medida que estén disponibles. Compruebe el estado.salesforce.com para más detalles.

2. August 21, 2026 at 9:57 PM UTCmonitoring

   La degradación de Salesforce invalidó activos Refresh Tokens, causando que los empleos de Copado pierdan acceso a sus orgs conectados. Para restaurar la funcionalidad, realice los siguientes pasos: 1. Reajuste sus credenciales de usuario de Copado para generar nuevas fichas de actualización válidas. 2. Retratar cualquier trabajo de Copado fallido. Si continúas experimentando cualquier problema después de volver a autenticar, por favor contacta con nuestro equipo de apoyo para recibir asistencia.

3. August 22, 2026 at 2:16 AM UTCresolved

   Hemos determinado que no hubo eventos adicionales en la última hora. Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 21, 2026 at 9:58 AM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a un subconjunto de clientes que están experimentando errores de autenticación Git cuando cometen o promueven componentes. Nuestro equipo de ingeniería está trabajando activamente para identificar la causa raíz y restaurar la funcionalidad normal lo antes posible. Seguiremos proporcionando actualizaciones a medida que se disponga de más información.

2. July 21, 2026 at 10:46 AM UTCidentified

   Hemos identificado que los errores de autenticación de Git que afectan a los clientes están relacionados con un incidente de servicio de GitHub en curso: https://www.githubstatus.com/ Estamos monitoreando de cerca y actualizaremos este estado cuando se disponga de más información.

3. July 21, 2026 at 12:09 PM UTCmonitoring

   El estado de GitHub ha sido actualizado para indicar que el incidente está resuelto. Monitorearemos por ahora y actualizaremos este incidente a Resolved una vez que hayamos confirmado que la funcionalidad completa está restaurada.

4. July 21, 2026 at 1:11 PM UTCresolved

   Hemos determinado que no hubo eventos adicionales en la última hora. Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 15, 2026 at 9:25 PM UTCinvestigating

   Hemos recibido informes de un pequeño número de clientes que experimentan problemas relacionados con los depósitos con sus tuberías CICD. Debido al patrón de estos informes, estamos investigando esto como una posible degradación de los servicios. Aunque sus operaciones específicas de Orgs y CICD no pueden ser impactadas, no dude en abrir un caso en nuestra Comunidad de Éxito si está experimentando problemas.

2. July 15, 2026 at 11:34 PM UTCresolved

   Esto ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 15, 2026 at 8:54 PM UTCinvestigating

   Estamos investigando informes de una cuestión que afecta a las promociones que implican la tubería de formato Metadata. Nuestro equipo de ingeniería está investigando activamente y proporcionará actualizaciones a medida que se disponga de más información. Nuestra próxima actualización llegará dentro de la hora.

Traducido automáticamente desde la actualización oficial del incidente.

1. May 11, 2026 at 3:23 PM UTCinvestigating

   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. May 11, 2026 at 3:44 PM UTCinvestigating

   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. May 11, 2026 at 7:05 PM UTCmonitoring

   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. May 11, 2026 at 8:21 PM UTCresolved

   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. May 5, 2026 at 2:58 PM UTCinvestigating

   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. May 5, 2026 at 3:59 PM UTCinvestigating

   We are continuing to investigate this issue.

3. May 5, 2026 at 4:00 PM UTCmonitoring

   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. May 5, 2026 at 8:07 PM UTCresolved

   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. October 20, 2025 at 3:45 PM UTCmonitoring

   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. October 20, 2025 at 4:40 PM UTCmonitoring

   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. October 20, 2025 at 9:10 PM UTCmonitoring

   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. October 20, 2025 at 11:32 PM UTCidentified

   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. October 21, 2025 at 1:06 AM UTCresolved

   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. August 18, 2025 at 4:32 PM UTCidentified

   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. August 18, 2025 at 7:03 PM UTCresolved

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

1. June 12, 2025 at 6:53 PM UTCinvestigating

   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. June 12, 2025 at 7:24 PM UTCinvestigating

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

3. June 12, 2025 at 8:08 PM UTCmonitoring

   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. June 12, 2025 at 8:55 PM UTCresolved

   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. March 3, 2025 at 10:35 PM UTCidentified

   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. March 4, 2025 at 1:34 PM UTCidentified

   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. March 4, 2025 at 3:06 PM UTCmonitoring

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

4. March 4, 2025 at 4:40 PM UTCresolved

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

1. November 27, 2024 at 11:06 PM UTCresolved

   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. July 18, 2024 at 10:23 AM UTCinvestigating

   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. July 18, 2024 at 3:01 PM UTCresolved

   This incident has been resolved.

1. July 18, 2024 at 1:50 AM UTCinvestigating

   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. July 18, 2024 at 2:38 AM UTCresolved

   This issue is now resolved.

1. June 28, 2024 at 6:49 PM UTCinvestigating

   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. June 29, 2024 at 1:44 AM UTCinvestigating

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

3. July 1, 2024 at 2:19 PM UTCresolved

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

1. April 24, 2024 at 1:13 PM UTCidentified

   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. April 24, 2024 at 2:38 PM UTCidentified

   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. April 24, 2024 at 6:11 PM UTCidentified

   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. April 25, 2024 at 2:53 AM UTCresolved

   This incident has been resolved.

1. January 23, 2024 at 5:55 PM UTCidentified

   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. January 23, 2024 at 9:11 PM UTCidentified

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

3. January 24, 2024 at 1:47 AM UTCresolved

   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. November 2, 2023 at 3:06 PM UTCidentified

   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. November 2, 2023 at 3:29 PM UTCidentified

   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. November 2, 2023 at 6:44 PM UTCidentified

   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. November 3, 2023 at 3:47 PM UTCresolved

   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. October 16, 2023 at 9:39 PM UTCinvestigating

   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. October 17, 2023 at 12:47 AM UTCidentified

   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. October 17, 2023 at 12:52 AM UTCmonitoring

   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. October 17, 2023 at 2:00 AM UTCresolved

   This incident has been resolved.

1. June 21, 2023 at 4:48 PM UTCidentified

   We are aware some clients are experiencing the following deployment error while deploying Apex Classes: ‘INVALID_OPERATION: runTests must not be empty when a testLevel of RunSpecifiedTests is used’ Our team has investigated and identified the issue. We are working to implement the necessary changes now; we will update the status of this incident once the issue is resolved. We apologize for any inconvenience.

2. June 21, 2023 at 5:09 PM UTCresolved

   This issue is now resolved. If you experienced this issue, be sure to create a NEW promotion record from the user story where you experienced the issue.