Istoricul incidentelor Copado

1. 16 septembrie 2026 la 08:47 UTCidentified

   Sumarul emisiunii: Forţele de vânzare au recunoscut oficial o întrerupere a serviciilor globale care afectează serviciile lor de bază. Această întrerupere a infrastructurii este cauza principală a erorilor intermitente de întreținere și a problemelor de acces care afectează în prezent mediile noastre. Starea actuală: Numărul de identificare al furnizorului: https://status.salesforce.com/incidente/20004433 Cauza root: Global Salesforce Central Service disruption. Următoarele etape și acțiuni: Urmăriți Actualizări Real-Time: Vă rugăm să monitorizați link-ul oficial de încredere al forțelor de vânzare pentru actualizări directe din inginerie. Suport Ticket Cerere: Va rugam sa continuati sa va abtineti de la deschiderea Copado Support sau bilete IT privind aceasta eroare specifica, deoarece echipele noastre de suport nu au control direct asupra restaurarii platformei suport. Monitorizăm îndeaproape progresul echipei şi vom posta o altă actualizare imediat ce funcţionalitatea platformei se stabilizează.

2. 16 septembrie 2026 la 12:19 UTCmonitoring

   Starea curentă Forțele de vânzare au implementat o fixare în întreaga lor infrastructură, iar serviciile revin în mod activ la normal în toate cazurile afectate. Echipa noastră a actualizat starea noastră de monitorizare ca platformă de performanță stabilizează. Progresul incidentului Restaurarea serviciului: În prezent, se află în curs de desfășurare o lansare la nivelul flotei de către forțele de vânzare, iar disponibilitatea sistemului este restabilită. Rezoluția permanentă: În paralel cu lansarea, echipele de inginerie implementează un fix permanent, la nivel de cod pentru a preveni recurența. Monitorizarea internă: Monitorizăm activ ratele de eroare și telemetria pentru a verifica stabilitatea completă. Orientări pentru clienți Majoritatea utilizatorilor ar trebui să aibă acum acces la cazurile lor Copado și Copado Community fără a întâmpina erori de întreținere. Dacă aveți orice latență reziduală sau sughiț scurt, vă rugăm să așteptați câteva momente și să reîmprospătați sesiunea browser-ului.

3. 16 septembrie 2026 la 18:03 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 27 august 2026 la 08:46 UTCinvestigating

   În prezent investigăm rapoarte de la un număr mic de clienți cu privire la execuția neașteptată de locuri de muncă. Echipa noastră analizează în mod activ comportamentul și lucrează pentru a înțelege mai bine problema. În timp ce investigăm în prezent acest lucru, vă rugăm să nu ezitați să deschideți un caz prin intermediul comunității noastre de succes dacă vă confruntați cu probleme conexe.

2. 27 august 2026 la 12:25 UTCinvestigating

   Încă investigăm în mod activ această problemă și lucrăm la o rezoluție. Vom actualiza acest statut cu mai multe informații pe măsură ce acesta devine disponibil.

3. 28 august 2026 la 06:12 UTCmonitoring

   Nu mai primim rapoarte despre execuţii neaşteptate. Lucrăm cu forţele de vânzări pentru a determina cauza principală şi vom continua să monitorizăm orice recidivă.

4. 28 august 2026 la 07:21 UTCresolved

   Am confirmat faptul că cauza principală a acestei probleme este un bug produs cunoscut. Forţele de vânzare lucrează în mod activ la o soluţie şi intenţionează în prezent să o pună la dispoziţie ca lansare timpurie. Detaliile pot fi găsite aici: https://help.salesforce.com/s/issue?id=a02g7000007hHG5AAM Semnăm acest incident ca fiind rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 21 august 2026 la 18:24 UTCinvestigating

   Urmărim în prezent degradarea serviciilor de vânzare care afectează autentificarea org şi implementarea Copado. Monitorizăm îndeaproape situația și vom furniza actualizări suplimentare pe măsură ce acestea devin disponibile. Verifica status.salesforce.com pentru detalii suplimentare.

2. 21 august 2026 la 21:57 UTCmonitoring

   Degradarea forţelor de vânzare a invalidat jetoanele active Refresh, ceea ce a făcut ca locurile de muncă din Copado să piardă accesul la orgile lor conectate. Pentru a restabili funcționalitatea, vă rugăm să efectuați următoarele etape: 1. Reautentificați acreditările de utilizator Copado pentru a genera noi, jetoane de reîmprospătare valide. 2. Rescrierea oricăror locuri de muncă Copado eșuate. Dacă continuați să experimentați orice probleme după re-autorizare, vă rugăm să ajungeți la echipa noastră de sprijin pentru asistență.

3. 22 august 2026 la 02:16 UTCresolved

   Am stabilit că nu au existat evenimente suplimentare în ultima oră. Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 21 iulie 2026 la 09:58 UTCinvestigating

   Investigăm în prezent o problemă care afectează un subset de clienți care se confruntă cu erori de autentificare Git atunci când comit sau promovează componente. Echipa noastră de inginerie este activ de lucru pentru a identifica cauza rădăcină și de a restabili funcționalitatea normală cât mai repede posibil. Vom continua să oferim actualizări pe măsură ce devin disponibile mai multe informații.

2. 21 iulie 2026 la 10:46 UTCidentified

   Am identificat că erorile de autentificare Git care afectează clienții sunt legate de un incident de serviciu GitHub în curs de desfășurare: https://www.githubstatus.com/ Monitorizăm îndeaproape și vom actualiza acest statut atunci când sunt disponibile mai multe informații.

3. 21 iulie 2026 la 12:09 UTCmonitoring

   Starea lui GitHub a fost actualizată pentru a indica că incidentul este rezolvat. Vom monitoriza deocamdată și vom actualiza acest incident pentru a soluționa odată ce am confirmat că funcționalitatea completă este restabilită.

4. 21 iulie 2026 la 13:11 UTCresolved

   Am stabilit că nu au existat evenimente suplimentare în ultima oră. Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 15 iulie 2026 la 21:25 UTCinvestigating

   Am primit rapoarte de la un număr mic de clienți care se confruntă cu probleme legate de depozit cu conductele lor CICD. Datorită modelului acestor rapoarte, investigăm în prezent acest lucru ca o posibilă degradare a serviciului. În timp ce operaţiunile dvs. specifice Orgs şi CICD nu pot fi afectate, vă rugăm să nu ezitaţi să deschideţi un caz în Comunitatea noastră de Succes dacă aveţi probleme.

2. 15 iulie 2026 la 23:34 UTCresolved

   Acest lucru a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 15 iulie 2026 la 20:54 UTCinvestigating

   Investigăm rapoarte privind o problemă care afectează promoţiile care implică conducta Formatului de Metadate. Echipa noastră de inginerie investighează activ și va oferi actualizări pe măsură ce mai multe informații devin disponibile. Următoarea actualizare va veni într-o oră.

Traducere automată din actualizarea oficială a incidentului.

1. 11 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 15:59 UTCinvestigating

   We are continuing to investigate this issue.

3. 5 mai 2026 la 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 mai 2026 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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 la 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 la 19:03 UTCresolved

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

1. 12 iunie 2025 la 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 iunie 2025 la 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 iunie 2025 la 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 iunie 2025 la 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 martie 2025 la 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 martie 2025 la 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 martie 2025 la 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 martie 2025 la 16:40 UTCresolved

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

1. 27 noiembrie 2024 la 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 iulie 2024 la 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 iulie 2024 la 15:01 UTCresolved

   This incident has been resolved.

1. 18 iulie 2024 la 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 iulie 2024 la 02:38 UTCresolved

   This issue is now resolved.

1. 28 iunie 2024 la 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 iunie 2024 la 01:44 UTCinvestigating

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

3. 1 iulie 2024 la 14:19 UTCresolved

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

1. 24 aprilie 2024 la 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 aprilie 2024 la 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 aprilie 2024 la 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 aprilie 2024 la 02:53 UTCresolved

   This incident has been resolved.

1. 23 ianuarie 2024 la 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 ianuarie 2024 la 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 ianuarie 2024 la 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 noiembrie 2023 la 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 noiembrie 2023 la 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 noiembrie 2023 la 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 noiembrie 2023 la 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 octombrie 2023 la 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 octombrie 2023 la 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 octombrie 2023 la 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 octombrie 2023 la 02:00 UTCresolved

   This incident has been resolved.