Copado driftsforstyrrelser

1. 27. august 2026 kl. 08.46 UTCinvestigating

   Vi undersøger i øjeblikket rapporter fra et lille antal kunder om uventede jobhenrettelser. Vores team er aktivt at gennemgå adfærd og arbejde for bedre at forstå problemet. Mens vi er i færd med at undersøge dette, er du velkommen til at åbne en sag gennem vores Success Fællesskab, hvis du oplever nogen relaterede spørgsmål.

2. 27. august 2026 kl. 12.25 UTCinvestigating

   Vi undersøger stadig aktivt dette spørgsmål og arbejder hen imod en beslutning. Vi opdaterer denne status med flere oplysninger, efterhånden som den bliver tilgængelig.

3. 28. august 2026 kl. 06.12 UTCmonitoring

   Vi modtager ikke længere rapporter om uventede jobhenrettelser. Vi arbejder med Salesforce for at bestemme den grundlæggende årsag og vil fortsætte med at overvåge for enhver gentagelse.

4. 28. august 2026 kl. 07.21 UTCresolved

   Vi har bekræftet, at årsagen til dette problem er en kendt Salesforce produkt fejl. Salesforce arbejder aktivt på et fix og planlægger i øjeblikket at gøre det tilgængeligt som en tidlig udgivelse. Detaljer kan findes her: https: / / help.savestigt.com / s / issue? id = a02g7000007hHG5AAM Vi markerer denne hændelse som løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. august 2026 kl. 18.24 UTCinvestigating

   Vi er i øjeblikket spore Salesforce service nedbrydning påvirker org godkendelse og Copado implementeringer. Vi overvåger situationen nøje og vil give yderligere opdateringer, efterhånden som de bliver tilgængelige. Tjek status.seleckraft.com for yderligere oplysninger.

2. 21. august 2026 kl. 21.57 UTCmonitoring

   Salesforce nedbrydningen ugyldiggjort aktive genopfriskningstokens, forårsager Copado job til at miste adgang til deres tilsluttede kugler. For at genoprette funktionalitet, skal du udføre følgende trin: 1. Genautentificer dine Copado-brugerlegitimation for at generere nye, gyldige opdateringstokens. 2. Prøv igen alle mislykkede Copado job. Hvis du fortsætter med at opleve nogen problemer efter re- autentificering, bedes du kontakte vores support team for hjælp.

3. 22. august 2026 kl. 02.16 UTCresolved

   Vi har besluttet, at der ikke var nogen yderligere hændelser i den sidste time. Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. juli 2026 kl. 09.58 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem påvirker en delmængde af kunder, der oplever Git autentificering fejl, når begå eller fremme komponenter. Vores ingeniørhold arbejder aktivt på at identificere årsagen og genoprette normal funktionalitet så hurtigt som muligt. Vi vil fortsætte med at levere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 21. juli 2026 kl. 10.46 UTCidentified

   Vi har identificeret, at Git autentification fejl påvirker kunderne er relateret til en igangværende GitHub service hændelse: https: / / www.githubstatus.com / Vi overvåger nøje og vil opdatere denne status, når der er flere oplysninger til rådighed.

3. 21. juli 2026 kl. 12.09 UTCmonitoring

   GitHub status er blevet opdateret til at indikere, at hændelsen er løst. Vi vil overvåge for nu og opdatere denne hændelse til Opløst, når vi har bekræftet, at fuld funktionalitet er genoprettet.

4. 21. juli 2026 kl. 13.11 UTCresolved

   Vi har besluttet, at der ikke var nogen yderligere hændelser i den sidste time. Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 15. juli 2026 kl. 21.25 UTCinvestigating

   Vi har modtaget rapporter fra et lille antal kunder, der oplever datarelaterede problemer med deres CICD-rørledninger. På grund af mønsteret i disse rapporter undersøger vi dette som en potentiel forringelse af tjenesten. Mens din specifikke Orgs og CICD operationer kan ikke blive påvirket, er du velkommen til at åbne en sag i vores Success Fællesskab, hvis du oplever problemer.

2. 15. juli 2026 kl. 23.34 UTCresolved

   Dette er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 15. juli 2026 kl. 20.54 UTCinvestigating

   Vi undersøger rapporter om et spørgsmål, der påvirker kampagner, der involverer Metadata Format Pipeline. Vores engineering team er aktivt at undersøge og vil give opdateringer som mere information bliver tilgængelig. Vores næste opdatering kommer inden for en time.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 11. maj 2026 kl. 15.23 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. 11. maj 2026 kl. 15.44 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. 11. maj 2026 kl. 19.05 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. 11. maj 2026 kl. 20.21 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. 5. maj 2026 kl. 14.58 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. 5. maj 2026 kl. 15.59 UTCinvestigating

   We are continuing to investigate this issue.

3. 5. maj 2026 kl. 16.00 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. 5. maj 2026 kl. 20.07 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. 20. oktober 2025 kl. 15.45 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. 20. oktober 2025 kl. 16.40 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. 20. oktober 2025 kl. 21.10 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. 20. oktober 2025 kl. 23.32 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. 21. oktober 2025 kl. 01.06 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. 18. august 2025 kl. 16.32 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. 18. august 2025 kl. 19.03 UTCresolved

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

1. 12. juni 2025 kl. 18.53 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. 12. juni 2025 kl. 19.24 UTCinvestigating

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

3. 12. juni 2025 kl. 20.08 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. 12. juni 2025 kl. 20.55 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. 3. marts 2025 kl. 22.35 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. 4. marts 2025 kl. 13.34 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. 4. marts 2025 kl. 15.06 UTCmonitoring

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

4. 4. marts 2025 kl. 16.40 UTCresolved

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

1. 27. november 2024 kl. 23.06 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. 18. juli 2024 kl. 10.23 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. 18. juli 2024 kl. 15.01 UTCresolved

   This incident has been resolved.

1. 18. juli 2024 kl. 01.50 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. 18. juli 2024 kl. 02.38 UTCresolved

   This issue is now resolved.

1. 28. juni 2024 kl. 18.49 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. 29. juni 2024 kl. 01.44 UTCinvestigating

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

3. 1. juli 2024 kl. 14.19 UTCresolved

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

1. 24. april 2024 kl. 13.13 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. 24. april 2024 kl. 14.38 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. 24. april 2024 kl. 18.11 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. 25. april 2024 kl. 02.53 UTCresolved

   This incident has been resolved.

1. 23. januar 2024 kl. 17.55 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. 23. januar 2024 kl. 21.11 UTCidentified

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

3. 24. januar 2024 kl. 01.47 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. 2. november 2023 kl. 15.06 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. 2. november 2023 kl. 15.29 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. 2. november 2023 kl. 18.44 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. 3. november 2023 kl. 15.47 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. 16. oktober 2023 kl. 21.39 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. 17. oktober 2023 kl. 00.47 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. 17. oktober 2023 kl. 00.52 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. 17. oktober 2023 kl. 02.00 UTCresolved

   This incident has been resolved.

1. 21. juni 2023 kl. 16.48 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. 21. juni 2023 kl. 17.09 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.