Salesforce: Salesforce Spiff Feature Disruption: Spiff
Affected components: Spiff1 instance
Timeline of updates
- investigating
We are investigating a potential cause of the issue.
- resolved
We’ve confirmed that the solution implemented to mitigate the issue causing the feature degradation was successful. Engineers have observed that the service is now stable and have declared the incident resolved. 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.
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
9cefb17fd8d61780…
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-09-14 16:10 UTC, resolved after 1.1 h, 2 update(s).
- Title
- Salesforce Spiff Feature Disruption: Spiff
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004429
Salesforce profileRecent Salesforce incidentsAll outages on September 14, 2026Salesforce in September 2026MarkdownJSON