Salesforce: Field Service Mobile Feature Degradation: Field Service Mobile
Affected components: Field Service Mobile999 instances
Timeline of updates
- update
Field Service Mobile customers using Android devices may have received an erroneous message campaign notification from Salesforce. This was a result of internal testing performed by Salesforce which was accidentally sent to customers. We've identified the faulty internal campaign, which incorrectly triggered these alerts for customers. This campaign has been removed and customers will no longer receive erroneous alerts.
We apologize for how this incident may have affected you and your business.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d530a7f586b128c3…
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Salesforce, started 2026-06-23 07:31 UTC, resolved after 1.0 h, 1 update(s).
- Title
- Field Service Mobile Feature Degradation: Field Service Mobile
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004163
Salesforce profileRecent Salesforce incidentsAll outages on June 23, 2026Salesforce in June 2026MarkdownJSON