Salesforce experienced a feature disruption lasting 7.8 hours that prevented users from creating new users via the user interface in sandbox environments across multiple instances in Brazil, Canada, USA, and Germany. The issue was caused by a database schema conflict following a recent release cycle. Salesforce resolved the incident by rolling forward to a new release version containing the necessary fixes, which was deployed in a phased rollout to all impacted instances.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
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.
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.
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.
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.
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.
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.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with