# Salesforce: Feature Service Disruption: B2 B2 CCommerce, Customer360 Audiences

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-04-21 21:30 UTC · Resolved: 2026-04-22 12:17 UTC · Duration: 15 h
- Updates: 6 · Affected components: B2 B2 CCommerce, Customer360 Audiences, 249 instances
- [Vendor status page: https://status.salesforce.com/incidents/20003952](https://status.salesforce.com/incidents/20003952)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-04-22 09:58 UTC: We’re investigating an issue impacting Data Cloud sandbox environments. Customers are unable to create or update records and may encounter an invalid type connection error. This issue doesn't impact production environment. Initial investigations indicate that a recent release is a trigger, and we're actively working on a fix.  We're rolling back the change in test environments to validate the fix. In the interim, customers can grant read access to the "Data Multi Org Connection" object to mitigate the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available
- **update** 2026-04-22 10:34 UTC: Further investigations indicate that Commerce Cloud is also impacted, with order ingestion into Salesforce Order Management failing in sandbox environments, blocking testing and go-live preparation.  The rollback has been completed in the test environment and the results are positive. We're now rolling back the change across all the remaining impacted instances.  We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-04-22 10:37 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.
- **update** 2026-04-22 11:13 UTC: We have now updated this Trust post to accurately reflect the impacted services.  We’re continuing the rollback on the remaining impacted instances and is estimated to complete at approximately 12:00 UTC. We apologize for any inconvenience this issue has caused.  We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-04-22 12:15 UTC: The rollback has been completed on all impacted instances as of 11:23 UTC and customers should no longer be affected by the issue. We'll monitor the service for a period of time to ensure the issue is fully resolved. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-04-22 12:25 UTC: After a period of monitoring and completing health checks, the team has confirmed that services have been fully restored as of 12:17 UTC.  We'll perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.


---
Canonical: https://rewindex.com/company/salesforce/incidents/20003952 · Markdown: https://rewindex.com/company/salesforce/incidents/20003952.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20003952 · Generated 2026-10-18T10:29:32.573Z