# Salesforce: Salesforce Spiff Feature Degradation: Spiff

> Salesforce status incident “Salesforce Spiff Feature Degradation: Spiff” on 2026-09-14: impact minor (vendor’s label), 35 d, 14 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/salesforce/incidents/20004430
Last updated: 2026-10-19T16:03:31Z

- Impact (vendor’s label): minor
- Status: resolved · edited after publishing
- Started: 2026-09-14 13:40 UTC · Resolved: 2026-10-19 15:57 UTC · Duration: 35 d
- Updates: 14 · Affected components: Spiff, 1 instance
- [Vendor status page: https://status.salesforce.com/incidents/20004430](https://status.salesforce.com/incidents/20004430)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **investigating** 2026-09-16 16:32 UTC: We are investigating a potential cause of the issue.
- **update** 2026-09-18 13:42 UTC: The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. We don’t have an estimated time for the completion of all workstreams at this point; however, we will provide an update every two business days or sooner if we have more information.
- **update** 2026-09-21 16:32 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- **update** 2026-09-23 20:13 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information
- **update** 2026-09-25 15:45 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- **update** 2026-09-28 16:12 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- **update** 2026-10-01 18:48 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information
- **update** 2026-10-05 21:18 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information
- **update** 2026-10-07 19:51 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information
- **update** 2026-10-09 15:14 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information
- **update** 2026-10-12 20:15 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- **update** 2026-10-13 17:50 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- **update** 2026-10-14 16:15 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.
- **update** 2026-10-15 23:27 UTC: We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update every 2 days or sooner if we have more information.

## Rewindex changes for this incident

- 2026-10-19 16:03 UTC: [Incident updated: Salesforce Spiff Feature Degradation: Spiff](https://rewindex.com/change/rf0bbc24f1e3f64.md)

## Cite this

Status incident (vendor impact label: minor) posted by Salesforce, started 2026-09-14 13:40 UTC, resolved after 35 d, 14 update(s); edited after publishing.

- Canonical URL: https://rewindex.com/company/salesforce/incidents/20004430
- Citation: Salesforce, “Salesforce Spiff Feature Degradation: Spiff” (2026-09-14 13:40 UTC). Archived by Rewindex: https://rewindex.com/company/salesforce/incidents/20004430 (CC BY 4.0).
- Markdown link: `[Salesforce: Salesforce Spiff Feature Degradation: Spiff (2026-09-14)](https://rewindex.com/company/salesforce/incidents/20004430)`


---
Canonical: https://rewindex.com/company/salesforce/incidents/20004430 · Markdown: https://rewindex.com/company/salesforce/incidents/20004430.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20004430 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T14:11:30.000Z