Live  /  Salesforce  /  Incident

Salesforce: Degradation: FieldServiceScheduling (296 instances)

Salesforce · salesforce.comMinor incidentResolved2026-11-12 16:16 UTC
Public — what happened

Summary

Salesforce said that customers using sandbox (testing) environments could not view or use their custom actions in the Field Service Lightning Dispatch and Scheduling Console, which could hold up some sandbox deployments. The company said production environments were not affected. It reported the problem starting around 12:31 UTC on 2026-11-12 and said a recent release change was the likely trigger, so it paused the rollout and began reversing the release. By 16:16 UTC Salesforce said the reversal was complete on almost all affected sandbox instances and customers there should be able to use their custom actions again, but one instance was still being worked on and the incident was not marked resolved.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Salesforce against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Salesforce: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Salesforce report →

More from Salesforce

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Salesforce status & history page.

Related: Salesforce status & history. SquidGrid is not affiliated with Salesforce.