# Salesforce: Feature Perf Degradation: MCGrowth

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-06-25 06:51 UTC · Resolved: 2026-06-25 12:00 UTC · Duration: 5.2 h
- Updates: 5 · Affected components: MCGrowth, 25 instances
- [Vendor status page: https://status.salesforce.com/incidents/20004165](https://status.salesforce.com/incidents/20004165)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-06-25 08:29 UTC: We’re investigating an issue impacting inbound SMS messaging for a subset of Marketing Cloud Growth & Advanced Editions on Core where customers are unable to receive inbound SMS messages or delivery receipts when end users reply to SMS. Outbound SMS messaging is not impacted. We’ve identified the trigger as a recent migration during which certain sender codes were not migrated correctly. The issue is limited to customers using the impacted sender codes. We’re applying the required configuration changes and validating the changes as they are deployed. We’ll provide another update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-06-25 08:55 UTC: We are implementing a code change to restore service. Before deployment, we’re validating the code changes to ensure it fully resolves the issue without creating additional impact. This validation is taking additional time. We’ll provide another update in 60 minutes or sooner if additional information becomes available.
- **update** 2026-06-25 09:55 UTC: Investigation has identified two contributing issues impacting inbound event processing. The first issue was caused by a synchronization gap that prevented a required configuration field from being propagated for a subset of sender codes. A remediation has been applied, and validation across multiple regions confirms inbound event processing has resumed for remediated codes. During the investigation, we identified a second issue impacting a subset of codes that were not fully synchronized between dependent systems. We've implemented a targeted remediation to backfill the missing data and reprocess impacted codes. The remediation is being validated on a limited set of records before being rolled out in phases to all impacted codes to ensure newly provisioned codes are not impacted by this synchronization issue. The implementations will take 2 to 3 hours and will provide an update as additional information becomes available.
- **update** 2026-06-25 11:35 UTC: We’ve successfully tested the remediation on a subset of codes to backfill the missing data and reprocess the codes. We're now in the process of performing the remediation to all impacted codes.  We'll provide the next update in 60 minutes or sooner if additional information becomes available.
- **update** 2026-06-25 12:08 UTC: We've completed the remediation steps as of 12:00 UTC. After monitoring and validating the service, we can confirm that all affected customers have been brought out of impact. We apologize for how this incident may have affected you and your business.


---
Canonical: https://rewindex.com/company/salesforce/incidents/20004165 · Markdown: https://rewindex.com/company/salesforce/incidents/20004165.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20004165 · Generated 2026-10-18T11:26:48.647Z