Salesforce: Salesforce Spiff Feature Degradation: Spiff

Impact: minorStatus: resolvedStarted 2026-08-24 16:55 UTCResolved 2026-08-25 14:56 UTC (22 h)21 updatesSource: status.salesforce.com

Affected components: Spiff1 instance

Timeline of updates

update2026-08-24 17:27 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 in 30 minutes or sooner if we have more information.
update2026-08-24 17:55 UTC
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.
update2026-08-24 18:30 UTC
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.
update2026-08-24 19:13 UTC
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.
update2026-08-24 19:42 UTC
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.
update2026-08-24 20:12 UTC
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.
update2026-08-24 20:31 UTC
We have observed that the impact on service health has decreased from a disrupted to a degraded state. We have amended the posting to reflect this and have highlighted the approximate timings of this transition.
update2026-08-24 21:01 UTC
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.
update2026-08-24 21:29 UTC
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.
update2026-08-24 22:01 UTC
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.
update2026-08-24 23:01 UTC
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.
update2026-08-24 23:35 UTC
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.
investigating2026-08-25 03:53 UTC
We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.
investigating2026-08-25 14:24 UTC
We are investigating a potential cause of the issue.
investigating2026-08-25 14:56 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 30 minutes or sooner if we have more information.
update2026-08-25 16:26 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 in 30 minutes or sooner if we have more information.
update2026-08-25 19:51 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 in 30 minutes or sooner if we have more information.
update2026-08-25 21:34 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 in 30 minutes or sooner if we have more information.
update2026-08-25 22:04 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 in 30 minutes or sooner if we have more information.
update2026-08-25 22:56 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 in 30 minutes or sooner if we have more information.
update2026-08-26 03:14 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 in 30 minutes or sooner if we have more information.

Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab). Salesforce profile · Recent Salesforce incidents · Markdown · JSON