Scenarios that require logout/login steps on the FSM app

Adding what we have identified so far being an one of the major pain point still for the field users. 

Short answer on your list:

First 4 require logout and login except LWC changes from to perform Clear Cache Metadata/Apply config changes . Page layout changes, layout assignments, user permissions, permission set and permission set group updates, new LWC actions, and updates to existing LWCs. All are metadata, and the app caches metadata at login. 

Why

The frequent sync everyone sees covers record data only. It does not cover cached metadata and code. A technician can be fully synced on data while still running a stale layout or LWC. 

The Apply Configuration Changes pop-up is generated by the app once it detects new metadata for the org. Timing is controlled by the app's internal polling cycle, which is why Salesforce documents it as appearing within 24 hours of login rather than immediately after deployment. Until the technician taps Apply Now or clears cached metadata, the device keeps running the previously cached configuration. 

Version 260 and earlier: manual clear required

Profile icon, gear icon, Advanced Settings, Clear Cached Metadata, OK.

Advanced Settings showing Clear Cached Metadata 

Version 262 and later: pop-up replaces manual clearing

Apply Configuration Changes pop-up

• Apply Now applies the configuration and refreshes metadata immediately
• Remind Me Later defers it and pins a notification in the Notification tab

Tapping outside the pop-up without choosing is treated the same as Remind Me Later. The pinned notification persists until the configuration is applied.

Pinned notification in the Notification tab

Current platform gaps

Admins cannot verify on a device whether the pop-up was shown or applied, cannot force a refresh remotely, and cannot attach the cache refresh to the data sync cycle. 

What we asked Salesforce

1. Can the pop-up be re-triggered manually instead of waiting for the polling window? Needed for P1 and P2 fixes. Open.
2. Does the pop-up cover metadata beyond LWC? Salesforce confirmed it applies to LWC only. They are evaluating extending it to Permission Sets, Profiles, Briefcase Builder, Public Groups, Static Resources, Apex, Page Layouts, Lightning Record Pages, Quick Actions, Buttons, Compact Layouts, Custom Metadata, Custom Settings, List Views, Tabs and Global Actions. Everything on that list still requires logout and login today.
3. Can we identify which users have applied the configuration? Needed so supervisors can follow up with technicians who have not. Open.

What we run with today

For any deployment changing mobile behavior we send both instructions, clear cache for 260 and earlier and Apply Changes for 262 and later, and we allow the 24 hour window before validating LWC fixes in production. If a device still shows the issue after a confirmed cache refresh, that is not stale cache and we treat it as a separate defect. We have a case open with Salesforce on that pattern.

Salesforce has indicated bug fixes for the LWC sync pop-up are targeted for September. 

Longer term

Product and Engineering have confirmed that auto triggering metadata sync on app close and reopen, with a fallback for users who miss the pop-up, is the right direction. Our ask is either to include cached metadata refresh in the standard Data Sync process, or to initialize the library only on SFS screen launch so the app always loads current configuration when opened. Either removes the dependency on technician action. 

No release commitment yet. We are tracking it and will post the roadmap response here. 

If you have additional asks we should put to Salesforce, add them below. Hope this helps!!!!