rewindex

CompaniesSalesforceIncidents

Salesforce: Feature Perf Degradation: Core Service

MinorStatus: resolvedStarted Resolved (1 min)10 updatesstatus.salesforce.com (opens in new tab)

Affected components: Core Service9 instances

Timeline of updates

  1. update

    We're aware of an issue impacting a subset of customers using DevOps pipeline automations. Customers are receiving an error “Apex test failure” when trying to perform deployments. We have identified that this issue may be a result of a recent release. We are evaluating whether it is possible to roll back to the last known healthy version to resolve this issue.

    We’ll provide an update in 30 minutes or sooner if additional information becomes available.

  2. update

    We'll perform a rollback of the recent release on a test instance. This is expected to take some time to complete and we'll be monitoring it’s progress.

    We’ll provide an update in 30 minutes or sooner if additional information becomes available.

  3. update

    The rollback of the recent release on a test instance is still underway. Additional teams have been engaged to assist with the rollback.

    We’ll provide an update in 30 minutes or sooner if additional information becomes available.

  4. update

    The rollback has been completed on one test instance. We are validating whether this has had positive results. In parallel, a configuration change is also being prepared to be tested as an alternative path to resolution. We have also updated the posting to reflect additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

    We’ll provide an update in one hour or sooner if additional information becomes available.

  5. update

    The release rollback on a test instance did not resolve the issue. We are preparing to perform a configuration change on another test instance in an effort to resolve the issue. We are also exploring additional resolution paths. We have not identified any viable workarounds that can be shared at this time.

    We’ll provide an update in 1 hour or sooner if additional information becomes available.

  6. update

    Following the release rollback, we confirmed that the issue persists for affected customers. Our engineering teams have identified the trigger for this incident and are exploring multiple resolution paths as a fix-forward strategy. We are currently preparing an emergency code fix and, in parallel, are validating a configuration change in sandbox environments to expedite the restoration of service. This is expected to take several hours to complete.

    We’ll provide another update as additional information becomes available.

  7. update

    Upon further investigation, the Salesforce Technology team has determined that the start time of impact is different than initially understood. We have now revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

  8. update

    The fix release testing is currently underway, and may take approximately four hours to complete. Once the fix release has been validated, we will roll this out across impacted instances. There is currently no time estimate for when the rollout will be completed.
    We’ll provide the next update once we can clarify the validation of the fix release testing, or when new information becomes available.

  9. update

    We’ve successfully validated the fix release via testing. The deployment to all the impacted instances is currently underway. The deployment is staggered to ensure minimal impact to users. This may take several hours to complete.
    We will provide the next update once we have visibility of the rollout progress or the rollout is complete.

  10. update

    Upon further investigation, we have determined that the instances listed in this Trust post were not impacted by this issue. We apologise for any unnecessary concern or inconvenience this may have caused.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Salesforce, started 2026-04-08 10:00 UTC, resolved after 1 min, 10 update(s).

Title
Feature Perf Degradation: Core Service
Vendor
Salesforce
Date
URL
https://rewindex.com/company/salesforce/incidents/20003941

Salesforce profileRecent Salesforce incidentsAll outages on April 8, 2026Salesforce in April 2026MarkdownJSON