# Salesforce: Salesforce Spiff Feature Disruption: Spiff

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2025-08-14 16:15 UTC · Resolved: 2025-09-18 22:29 UTC · Duration: 35 d
- Updates: 10 · Affected components: Spiff, 1 instance
- [Vendor status page: https://status.salesforce.com/incidents/20003156](https://status.salesforce.com/incidents/20003156)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **investigating** 2025-08-14 17:46 UTC: We’re investigating the cause of the issue. We will provide an update in 1 hour or sooner if we have more information.
- **investigating** 2025-08-14 18:46 UTC: We’re investigating the cause of the issue and have engaged more engineers to help isolate the root cause. We will provide an update in 1 hour or sooner if we have more information.
- **update** 2025-08-14 18:47 UTC: Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.
- **investigating** 2025-08-14 19:56 UTC: We are still investigating the cause of the issue.
- **investigating** 2025-08-15 16:34 UTC: We’re investigating the cause of the issue and have engaged more engineers to help isolate the root cause. We will provide an update later today when have more information.
- **investigating** 2025-08-15 23:06 UTC: We are investigating a potential cause of the issue. We will provide an update Monday morning, August 18th, by 10am MDT.
- **update** 2025-08-18 16:23 UTC: We isolated the issue to the application tier and are working to find the best path to resolution. We will provide an update by 4PM MDT or sooner if we have more information.
- **investigating** 2025-08-20 00:34 UTC: We're continuing to investigate the issue and are making steady progress. We thank you for your patience and will have another update tomorrow.
- **update** 2025-09-05 15:09 UTC: A few customers are still impacted by this issue and investigation for them is ongoing.
- **resolved** 2025-09-18 22:28 UTC: The Salesforce Technology team has observed that instance stability and performance are now at expected levels and declared the incident resolved. We will thoroughly investigate the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.


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