Search

Companies / Salesforce / incidents

Salesforce: Feature Service Disruption: Core Service

Impact: minorStatus: resolvedStarted Resolved (3 d)4 updatesSource: status.salesforce.com (opens in new tab)

Affected components: Core Service4 instances

Timeline of updates

  1. update

    We are investigating a feature disruption affecting a subset of customers using third-party legacy auth tokens for nested app authentication. Customers using the third-party Mail engagement feature are currently unable to authenticate. Initial investigations show that the issue was potentially triggered by a recent change with a third-party service provider. We are actively exploring multiple paths to resolution. We will provide an update in 30 minutes or sooner if additional information becomes available.

  2. update

    We are working with the third-party service provider to resolve the issue and are simultaneously working on a fix to update service-level outbound access guardrails. We will provide an update in 60 minutes or sooner if additional information becomes available.

  3. update

    The fix is currently being deployed and is estimated to take two hours. It is expected to update service-level outbound access guardrails. We are actively working to restore services. We will provide an update in two hours or sooner if additional information becomes available.

  4. update

    We’ve confirmed that the solution implemented to mitigate the issue causing the feature disruption was successful. After a period of performance monitoring and comprehensive health checks, the services were fully restored at 19:31 UTC. Customers should now be able to authenticate using the third-party Mail engagement feature without issue. After further investigation, the incident's start time has been revised from September 19, at 16:53 UTC, to September 16, at 11:00 UTC, to more accurately reflect the time customers may have begun to experience the impact. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

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