Companies / Salesforce / incidents

Salesforce: Feature Service Disruption: Analytics, Core Service

Affected components: AnalyticsCore Service179 instances

Timeline of updates

1. update2026-03-16 22:49 UTC

   At 21:33 UTC on March 16, 2026, a feature disruption began affecting select features on multiple instances. As a result, a subset of customers may be unable to use CRM Analytics recipe jobs on impacted instances. Our teams are actively investigating and working to restore full service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

2. update2026-03-16 23:24 UTC

   We continue to investigate this issue, and multiple technical teams are actively engaged to troubleshoot. We are also reviewing the scope of impact as this may be broader than originally understood. A service restart was undertaken, however, this did not restore services. We are working to manually increase the resource limits to try to restore normal operations. We are also reviewing all recent changes to see whether this may be contributing to this issue. Users may continue to be unable to obtain new certificates, and specific features may currently be impacted. We'll provide an update in 60 minutes or sooner if additional information becomes available.

3. update2026-03-17 00:29 UTC

   Upon further investigation, we have 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.

4. update2026-03-17 00:31 UTC

   Upon further investigation, we identified that additional features across multiple cells, including Search, Managed Operations (MO), and continued APT performance were impacted by this issue. Resource limits were subsequently increased across all affected cells, which successfully restored performance levels for customers. Based on this recovery, the issue is considered resolved as of 00:12 UTC on March 17, 2026. We’ll perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a recurrence. We apologize for how this incident may have affected you and your business.

Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab). Salesforce profile · Recent Salesforce incidents · Markdown · JSON