feature Service Disruption (20004592)

Updates (6)

1. 11-11-2026 21:39
   feature Service Disruption (20004592)

   The feature disruption affecting Apex code compilation and deployment is resolved. We rolled affected instances back to the previous version, and all instances are now running on it. Customers can compile and deploy Apex code again. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the underlying cause, and preventive action to avoid a repeat in the future.

   Salesforce ↗
2. 11-11-2026 21:13
   feature Service Disruption (20004592)

   We've nearly finished rolling back the affected instances to the previous version. A few instances needed a second attempt, and we've now completed those. We're closely monitoring the small number of instances that are still finishing. Customers on those instances may still see intermittent failures when compiling or deploying Apex code. We’ll provide another update in 60 minutes or sooner if additional information becomes available.

   Salesforce ↗
3. 11-11-2026 20:45
   feature Service Disruption (20004592)

   We continue to address a feature disruption affecting a subset of customers on instances that received a recent software release. Several rollbacks have completed, and recovery has been confirmed on a prioritized affected instance. Validation is underway on additional instances while the broader rollback continues. Until the rollback completes, some customers may continue to experience intermittent failures, when compiling or deploying Apex code. Depending on how the affected code is used, login flows and related business processes may also fail. We’ll provide another update in 60 minutes or sooner if additional information becomes available.

   Salesforce ↗
4. 11-11-2026 20:19
   feature Service Disruption (20004592)

   We have started rolling affected instances back to the previous version, prioritizing the environments with confirmed customer impact. The broader rollback is now in progress, and teams will validate recovery as each instance completes. We're also preparing a corrective release that removes the triggering runtime-library change before the affected release is deployed again. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

   Salesforce ↗
5. 11-11-2026 19:55
   feature Service Disruption (20004592)

   We are investigating a feature disruption affecting some customers on instances that received a recent release. Affected customers may experience failures when compiling or deploying Apex code. In some cases, customers may also be unable to log in or complete processes that depend on the affected Apex code. The behavior is intermittent and depends on the specific code being compiled. We've identified an update to a supporting runtime library in the recent release as the likely trigger. Further deployment of the release has been halted, and teams are working to return affected instances to the previous version. A corrective release is also being prepared as a fallback. We’ll provide another update in 30 minutes or sooner if additional information becomes available.

   Salesforce ↗
6. 11-11-2026 19:34
   feature Service Disruption (20004592)

   During investigations, we established that the level of impact differs from what was initially understood. We have updated the incident posting to reflect the current impact symptoms accurately.

   Salesforce ↗