# Salesforce: Feature Service Disruption: B2 BCommerce

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-09-24 23:59 UTC · Resolved: 2026-09-25 06:08 UTC · Duration: 6.2 h
- Updates: 10 · Affected components: B2 BCommerce, 449 instances
- [Vendor status page: https://status.salesforce.com/incidents/20004448](https://status.salesforce.com/incidents/20004448)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-09-25 02:50 UTC: 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.
- **update** 2026-09-25 02:58 UTC: We identified a certificate expiry issue, disrupting requests to the Discovery service and causing search and index rebuild failures. We're validating certificate status across all impacted environments before rotating the certificate to restore service. We've also identified additional environments experiencing this issue and are expanding our scope of investigation. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-09-25 03:21 UTC: We've confirmed that certificate expiry triggered the issue and are now rotating certificates to restore service. This continues to affect search index rebuilds for a subset of B2B Commerce customers. We're generating new certificates for the affected regions. We'll first rotate the certificate in one region to validate the fix, then roll it out across the remaining affected regions in parallel.  We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-09-25 03:56 UTC: We’ve generated the certificates required for rotation and are now working on the activation requests. The issue continues to affect search index rebuilds for a subset of B2B Commerce customers. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.
- **update** 2026-09-25 04:22 UTC: We've rotated the certificate in the first affected region and updated the search service. We're now validating the logs to confirm the fix before rolling out the certificate rotation across the remaining affected regions in parallel.  We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-09-25 05:21 UTC: We're still validating the rotated certificate in the first affected region. We've also identified this issue affecting additional environments and are expanding our investigation to determine the full scope of impact.  We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-09-25 05:31 UTC: 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.
- **update** 2026-09-25 06:06 UTC: We completed a certificate rotation and restarted application services in the first affected region, and validation confirmed this was successful. We're now rolling out the certificate rotation across the remaining affected regions in parallel.  We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-09-25 06:28 UTC: We resolved the search index errors affecting some B2B Commerce customers. We confirmed successful certificate rotation and service restoration across all affected regions, and customers can now rebuild search indexes normally. We apologize for how this incident affected you and your business.  We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
- **update** 2026-09-25 06:37 UTC: Upon further investigation, we've determined that the start time of impact is different than initially understood. We've 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.


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