Changes / Salesforce / Field Service Scheduling Feature Disruption: Field Service Scheduling
Salesforce: Major incident: Field Service Scheduling Feature Disruption: Field Service Scheduling
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: outage (model (Jev), 82%)Changed Detected Source: status.salesforce.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: Field Service Scheduling Feature Disruption: Field Service Scheduling
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-01-12 07:53 UTC
Before: not present
After: 2026-01-12 11:49 UTC
Before: not present
After: 89 instances, Field Service Scheduling
Before: not present
After: A subset of customers in the EU region are experiencing timeouts when using the Field Service Scheduling service. Affected customers may receive HTTP 503 errors along with connection and timeout errors, and may not be able to perform async field service scheduling.
We’ll provide an update in 30 minutes or sooner when the information becomes available.
Before: not present
After: Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
Before: not present
After: Additional instances have been identified under impact, and we've updated the posting to reflect the same.
Before: not present
After: High memory utilization resulted in connection limits being reached. We have increased capacity and are seeing improved performance. We'll continue to monitor until service returns to normal operating levels.
We’ll provide an update in 30 minutes or sooner when the information becomes available.
Before: not present
After: Some customers have reported that the service is operating normally, while others continue to observe intermittent errors and timeouts. We will continue to monitor the service to ensure that the issue resolves for all affected customers.
Additional instances have been identified under impact, and we've updated the posting to reflect the same.
We’ll provide an update in 60 minutes or sooner when the information becomes available.
Before: not present
After: The issue is resolved and customers can now use Field Service Scheduling as expected. To resolve the issue we increased capacity and removed a resource found to be contributing to delays.
Additional instances have been identified that impacted by this issue and we've updated the posting to reflect the same.
We apologize for how this incident affected you and your business. We will undertake a full investigation to establish the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Field Service Scheduling Feature Disruption: Field Service Scheduling (this change) | Major incident |
All Salesforce changes → · Salesforce profile · Markdown · JSON