← Live dashboard

feature Service Disruption (20004593)

ResolvedminorOfficial source confirmedFirst recorded update 12-11-2026 00:58 · Resolved 12-11-2026 17:23

The issue affecting custom actions in the Field Service Lightning (FSL) Dispatch and Scheduling Console in sandbox environments is now resolved. At 16:23 UTC, we completed the rollback of the release on all impacted sandbox instances. Customers can once again view and use their custom actions and resume any blocked sandbox deployments. Production environments weren't affected. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a...

Salesforce live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

View all comments
    Having problems with Salesforce now? Check the current status

    Updates (7)

    1. 12-11-2026 17:35
      feature Service Disruption (20004593)

      The issue affecting custom actions in the Field Service Lightning (FSL) Dispatch and Scheduling Console in sandbox environments is now resolved. At 16:23 UTC, we completed the rollback of the release on all impacted sandbox instances. Customers can once again view and use their custom actions and resume any blocked sandbox deployments. Production environments weren't affected. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

      Salesforce ↗
    2. 12-11-2026 17:16
      feature Service Disruption (20004593)

      The rollback is complete on almost all impacted sandbox instances. Customers on those instances should now be able to view and use their custom actions in the FSL (Field Service Lightning) Dispatch and Scheduling Console. One remaining instance is taking longer than expected, and our teams are actively working to complete its rollback. Production environments aren't affected. We'll provide an update in 60 minutes or sooner if additional information becomes available.

      Salesforce ↗
    3. 12-11-2026 16:31
      feature Service Disruption (20004593)

      We're still rolling back the release across all sandbox instances that received it, and we're monitoring its progress closely. We'll provide an update in 60 minutes or sooner if additional information becomes available.

      Salesforce ↗
    4. 12-11-2026 15:41
      feature Service Disruption (20004593)

      The rollback is taking longer than anticipated. This is due to a subset of instances requiring a manual rollback by our team. Despite this delay, the overall rollback is progressing well. We'll provide an update in 60 minutes or sooner if additional information becomes available.

      Salesforce ↗
    5. 12-11-2026 14:48
      feature Service Disruption (20004593)

      We're continuing to roll back the release on sandbox instances. We're monitoring its progress and have additional resources on standby in case the rollback doesn't succeed. We'll provide an update in 60 minutes or sooner if additional information becomes available.

      Salesforce ↗
    6. 12-11-2026 13:56
      feature Service Disruption (20004593)

      We’ve completed the testing of the rollback and have validated that it was succesful. We’re working to perform a rollback on all impacted instances which received the release. This is expected to several hours to complete. We will continue to monitor it’s progress. We'll provide an update in 60 minutes or sooner if additional information becomes available.

      Salesforce ↗
    7. 12-11-2026 13:32
      feature Service Disruption (20004593)

      We're aware of an issue affecting the Field Service Lightning (FSL) Dispatch and Scheduling Console in sandbox environments. Customers can’t view or use their custom actions, which may block some sandbox deployments. Production environments aren’t affected. We’ve identified a recent release change as the likely trigger of the issue. We've paused further rollout of the release. We’re testing a rollback of the release to see if this brings customers out of impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.

      Salesforce ↗

    What to do next

    • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
    • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
    • Watch the provider going forward. Follow Salesforce's status feed →

    GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.