--- schema_version: "1" id: 4225433e1f68f67e1fab83da7d40786c8ff7821d049a8899e14b7d4f3ed1fc7a title: Offline Priming FAQ for the Field Service Mobile App in Workforce Scheduling collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/wfs_mobile_offline_priming_faq.md canonical_url: https://help.salesforce.com/s/articleView?id=service.wfs_mobile_offline_priming_faq.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 1f647786602c97739dd62bba89955b7a4b2c6430d19751be1d2b26ae13dc2ebe description: Find answers to common questions about offline priming for the Field Service mobile app. products: - Public Sector - Service Cloud release: "264" --- # Offline Priming FAQ for the Field Service Mobile App in Workforce Scheduling Find answers to common questions about offline priming for the Field Service mobile app. ### Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions
## What are drafts? When records are created, updated, or deleted in the Field Service mobile app, each change is recorded as a draft and queued to sync back to your org. This process happens whether the device is online or offline. If the device is online, the app syncs drafts immediately. Otherwise, it syncs them when the device is back online. On custom Lightning pages, drafts come from record forms and from create, update, and delete actions. ## How are drafts synced? When the connection returns, drafts sync in the order the worker created them. Salesforce applies the change at sync time, not at the time the worker saved it on the device. Created date and last modified date reflect that sync. Triggers and other automations run then, too. Drafts don't check for newer edits already in Salesforce. The change that reaches Salesforce last is the one that remains. A worker who syncs after someone else edited the same record overwrites that edit. ## Why didn't a draft sync, and what should mobile workers do about it? A draft can fail to sync for several reasons. - Server validation rejected a field value. Those checks run only in Salesforce, and they can involve more than one field. - The record changed after the draft was saved. The sync fails when the draft updates a record that was deleted. - To delete the failed draft and revert its changes, the mobile worker needs to tap **Undo**. To correct a validation failure, tap **Edit**. **Edit** is available when the object has an `.edit` quick action. ## How are sync conflicts handled? When a sync conflict occurs, the most recent change uploaded to the Salesforce server takes precedence. A conflict pauses the Pending Uploads queue. Mobile workers should delete the pending upload, or tap the item and edit the data. The queue continues after that conflict is resolved. ## How are appointment changes handled? When appointment schedules change, mobile workers receive a text notification. If the app is in the foreground or background when the mobile worker gets a notification, the service appointment is automatically primed. If the app isn't running, the service appointment and any associated records aren't updated and primed until the mobile worker opens the app and taps the notification. ## How can mobile workers fix priming errors? A network error stops priming and shows an error message on the mobile app. After the connection returns, users should resync the app from the offline priming screen. Priming also stops when Salesforce receives too many requests at once. Users should wait briefly, then try again. An ID error in Briefcase Builder means the ID is set incorrectly. Contact your Salesforce admin or Salesforce Customer Support.