# Salesforce: B2 B2 CFeature Disruption: B2 CCore

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-02-09 15:00 UTC · Resolved: 2026-02-22 11:30 UTC · Duration: 13 d
- Updates: 7 · Affected components: B2 CCore, 38 instances
- [Vendor status page: https://status.salesforce.com/incidents/20003714](https://status.salesforce.com/incidents/20003714)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-02-20 20:10 UTC: We're aware of an issue impacting customers using Order Capture Interface version 26.2. Users may experience issues with records in Business Manager and receive out of stock errors. We are investigating the cause and exploring multiple paths to resolution. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-02-20 20:36 UTC: Upon investigation, we determined that a change from February 20, 2026 as the potential trigger of the issue.  In addition, this issue may manifest after running a full availability index rebuild job. The team is investigating to determine if a new patch would be the best path forward to resolution. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-02-20 21:12 UTC: We continue to investigate the issue and have determined that a fix-forward will be the best path to remediation. We are currently developing the patch and we'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-02-20 21:48 UTC: We continue to investigate the issue and develop the patch. We’ll provide an update when the deployment has commenced.
- **update** 2026-02-20 22:54 UTC: Further investigation into the root cause of the issue has determined that the impact started when a change was deployed on February 9, 2026. We have updated the incident details to reflect this new understanding. We continue to investigate this incident and work towards developing and deploying the patch. We’ll provide an update when the deployment has commenced.
- **update** 2026-02-21 03:46 UTC: We have successfully validated and tested the fix on the POD311. Initial reports have indicated positive results, and services were restored to normal operating levels for the verification PODS. The team is deploying the fix to the remaining PODS. We’ll provide an update when the deployment is completed.
- **resolved** 2026-02-22 11:35 UTC: We’ve confirmed that the solution implemented to mitigate the issue causing the feature disruption was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate 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/20003714 · Markdown: https://rewindex.com/company/salesforce/incidents/20003714.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20003714 · Generated 2026-10-18T09:36:24.989Z