Salesforce: Performance Degradation: Core Service
Affected components: Core Service34 instances
Timeline of updates
- update
Between 03:30 UTC on April 14 and 01:26 UTC on April 15, a subset of customers experienced an issue where Triggered Flows didn't function as expected. This resulted in significantly slower response times when creating or updating records via the User Interface or Integration Tools, and impacted services including Live Chat, Flows, Order Intake, and Case Creation.
All impacted instances have been successfully rolled back to the last known good version and the issue stands resolved.
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
0f978d4a57e1b448…
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-14 03:30 UTC, resolved after 22 h, 1 update(s).
- Title
- Performance Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003935
Salesforce profileRecent Salesforce incidentsAll outages on April 14, 2026Salesforce in April 2026MarkdownJSON