Salesforce: Feature Perf Degradation: Customer360 Audiences
Affected components: Customer360 Audiences23 instances
Timeline of updates
- update
We're aware of an issue that affected a subset of customers where search index builds triggered between 21:45 UTC on July 14 and 00:32 UTC on July 16 are stuck in the ‘submitted’ status. We've implemented a fix to ensure that builds triggered outside of this time will be processed correctly. The code fix was successfully deployed and customers are no longer impacted as of 00:32 UTC on July 16.
We apologize for how this incident may have affected you and your business.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a1681bae36ba4c9f…
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Salesforce, started 2026-07-14 21:45 UTC, resolved after 27 h, 1 update(s).
- Title
- Feature Perf Degradation: Customer360 Audiences
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004278
Salesforce profileRecent Salesforce incidentsAll outages on July 14, 2026Salesforce in July 2026MarkdownJSON