# Salesforce: Feature Perf Degradation: Core Service - Impact (vendor’s label): minor - Status: resolved - Started: 2026-06-29 05:45 UTC · Resolved: 2026-06-30 22:00 UTC · Duration: 40 h - Updates: 13 · Affected components: Core Service, 52 instances - [Vendor status page: https://status.salesforce.com/incidents/20004173](https://status.salesforce.com/incidents/20004173) - [Company: Salesforce](https://rewindex.com/company/salesforce.md) ## Timeline of updates - **update** 2026-06-30 06:00 UTC: We're aware of an issue impacting Event Log File delivery for customers with Salesforce Shield licensing. As a result, customers may experience delays in receiving Event Log Files. We are actively investigating and working toward a resolution. We'll provide an update in 30 minutes or sooner if additional information becomes available. - **update** 2026-06-30 06:26 UTC: We've identified a recent configuration change as the likely trigger for Event Log File delivery. We're exploring multiple paths to ‌resolution. We’ll provide an update in 30 minutes or sooner if additional information becomes available. - **update** 2026-06-30 07:15 UTC: We have completed an initial rollback of the recent configuration changes in a test environment and are currently validating whether this resolves the issue Post-validation we'll apply the configuration changes to the remaining impacted instances. We'll provide another update in 30 minutes or sooner if additional information becomes available. - **update** 2026-06-30 07:36 UTC: Further investigation revealed that the recent configuration changes had reduced processing capacity, which has triggered ‌the delays of the Event Log Files. We've hit an issue with rolling back the configuration change. We're evaluating options to create an emergency fix which will add the necessary capacity to handle requests. Additional teams are being engaged to assist with developing this fix. There's currently no work-around available to customers. We'll provide another update in 60 minutes or sooner if additional information becomes available. - **update** 2026-06-30 08:14 UTC: We’ve completed a capacity increase and are now validating whether it has had a positive effect on the impacted instances.In parallel, we’re forcing a restart to ensure the infrastructure correctly routes to the new capacity. We'll provide another update in 60 minutes or sooner if additional information becomes available. - **update** 2026-06-30 08:49 UTC: We haven’t seen improvement in the service following the increase in capacity. The infrastructure appears to be reading from a cached configuration of previous lower capacity limits. We are performing a change to ensure the infrastructure recognizes the correct increased capacity limits. We'll provide another update in 60 minutes or sooner if additional information becomes available. - **update** 2026-06-30 09:32 UTC: We're continuing to perform the necessary configuration changes to the infrastructure to allow it to recognize the increased capacity limits. We’ll monitor the changes to validate whether they're successful. We'll provide another update in 60 minutes or sooner if additional information becomes available. - **update** 2026-06-30 10:11 UTC: Work is still underway to complete configuration changes which we believe should bring customers out of impact. We'll provide another update in 60 minutes or sooner if additional information becomes available. - **update** 2026-06-30 11:13 UTC: We have completed the configuration steps and have observed that the backlog in processing Event Log Files is reducing. We are continuing to monitor it’s progress. We'll provide another update in 60 minutes or sooner if additional information becomes available. - **update** 2026-06-30 12:09 UTC: During recovery, we identified that additional remediation was required for a small portion of Event Log File processing. We restarted the affected processing pipelines and are continuing to monitor processing volumes to confirm full recovery. We are actively working to ensure processing returns to normal and will provide an update within 60 minutes, or sooner if additional information becomes available. - **update** 2026-06-30 13:22 UTC: We are actively monitoring the recovery to ensure the processing backlogs continue to clear as expected. Due to a large backlog, processing of pending Event Log Files will take several hours. Files are being processed in order, and the backlog is gradually reducing. We'll provide an update when there are significant changes, or sooner if additional information becomes available. - **update** 2026-06-30 15:03 UTC: We continue to closely monitor the recovery process to ensure that progress in resolving Event Log File delivery delays remains on track for affected customers. The backlog is reducing, with completion expected to take several hours. We'll provide an update when there are significant changes, or sooner if additional information becomes available. - **update** 2026-06-30 22:15 UTC: The backlog of Event Log Files has successfully been processed to within normal service parameters. The service is now fully operational, and customers should no longer experience abnormal delays in receiving Event Log Files. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. --- Canonical: https://rewindex.com/company/salesforce/incidents/20004173 · Markdown: https://rewindex.com/company/salesforce/incidents/20004173.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20004173 · Generated 2026-10-18T10:29:25.432Z