Salesforce: Feature Perf Degradation: Core Service
Affected components: Core Service11 instances
Timeline of updates
- update
A subset of customers using DevOps pipeline automations experienced an "Apex test failure" error when attempting deployments. As a result scratch org creation via DevOps pipelines was blocked. The issue was traced to a recent release. After confirming that a rollback didn't resolve the problem, our engineering teams pivoted to a fix-forward strategy, developing and validating an emergency code fix in parallel with a configuration change in sandbox environments. Once validated, the fix was deployed across all impacted instances. The issue is fully resolved.
We sincerely apologize for the inconvenience this has caused.
- update
Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact. We apologize for any inconvenience 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.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
fed006e8c9bfbd8f…
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 9 d, 2 update(s).
- Title
- Feature Perf Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003943
Salesforce profileRecent Salesforce incidentsAll outages on April 8, 2026Salesforce in April 2026MarkdownJSON