Search

Companies / Salesforce / incidents

Salesforce: Feature Service Disruption: Core Service

Impact: minorStatus: resolvedStarted Resolved (12 h)9 updatesSource: status.salesforce.com (opens in new tab)

Affected components: Core Service36 instances

Timeline of updates

  1. update

    Upon further investigation, the Salesforce Technology team has 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.

  2. update

    At 10:00 UTC on April 22, 2026, we began investigating a feature disruption affecting multiple sandbox environments. As a result, users may be unable to create new users via the user interface or may encounter an error. We are currently investigating this issue. We will provide an update in 60 minutes, or sooner if additional information becomes available.

  3. update

    We continue to investigate the feature disruption affecting Sandbox environments. Our engineering teams have determined that the issue is related to a database schema conflict following a recent release cycle. We are currently evaluating a path to resolve the disruption and working on a fix. We will provide an update in 60 minutes, or sooner if additional information becomes available.

  4. update

    We have identified a path to resolution by rolling forward to a new release version, which contains the necessary fixes. We are currently finalizing the build for this version and expect to begin a test deployment to a single instance soon. Upon successful verification, we will proceed with a broader rollout to all impacted instances which may take several hours to complete. We will provide an update in 60 minutes, or sooner if additional information becomes available.

  5. update

    Upon further investigation, the Salesforce Technology team has 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.

  6. update

    We are currently in the process of finalizing the associated release build. Once the build is complete, we will begin a targeted deployment to a single instance to verify the resolution in the environment. Following successful verification, we will initiate a phased rollout to all remaining impacted instances We will provide an update upon significant development, or sooner if additional information becomes available.

  7. update

    Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

  8. update

    Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

  9. update

    As of 02:43 UTC on April 23, 2026, ‌incident is resolved. We identified an issue at database tier introduced by a recent release. We validated a fix in a lower environment, and deployed it across all impacted instances. After successful validation, it was rolled out to impacted sandbox instances, fully resolving ‌impact. We apologize for how you and your business may have been affected by this incident.

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