# Salesforce: Feature Service Disruption: Field Service Mobile

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-05-19 23:50 UTC · Resolved: 2026-05-20 04:14 UTC · Duration: 4.4 h
- Updates: 3 · Affected components: Field Service Mobile, 5 instances
- [Vendor status page: https://status.salesforce.com/incidents/20004031](https://status.salesforce.com/incidents/20004031)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-05-20 01:38 UTC: At 23:50 UTC on May 19, 2026 we began investigating a feature disruption impacting Salesforce Field Service (SFS) Mobile Services. Impacted customers may receive 403 error messages when trying to use the performance priming feature. We are in the process of deploying a fix to remediate the issue and this is expected to take approximately 60 minutes. We’ll provide an update in the next 60-90 minutes or sooner if new information, or validation of the fix, becomes available.
- **update** 2026-05-20 04:06 UTC: We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update once the fix has been deployed and validated, or sooner if we have more information.
- **update** 2026-05-20 04:37 UTC: We’ve confirmed that the solution implemented to mitigate the issue causing the feature disruption was successful. We have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apologize for how you and your business may have been affected by this incident.


---
Canonical: https://rewindex.com/company/salesforce/incidents/20004031 · Markdown: https://rewindex.com/company/salesforce/incidents/20004031.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20004031 · Generated 2026-10-18T10:29:32.299Z