Salesforce: Feature Perf Degradation: Core Service
Affected components: Core Service1 instance
Timeline of updates
- update
We identified an issue where a background process related to custom field deletion generated an unusually high volume of Change Data Capture (CDC) events. This resulted in delays in CDC event processing for a subset of customers.
The process was paused to allow the backlog to clear. CDC processing has returned to normal levels, and the issue is now resolved.
You would have previously received a separate notification for this issue. This posting is to inform you of the accurate start and end time for your instance.We will perform a full investigation of this incident to confirm the technical trigger, identify the underlying cause, and implement preventive measures to avoid recurrence. We apologize for any impact this may have caused to you and your business.
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
d52ccba9f04ab88c…
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-03-10 07:24 UTC, resolved after 2 d, 1 update(s).
- Title
- Feature Perf Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003831
Salesforce profileRecent Salesforce incidentsAll outages on March 10, 2026Salesforce in March 2026MarkdownJSON