Salesforce Field Service (SFS) Mobile App — Users Remain Logged In After Configured Session Timeout Expires (Working As Designed)

When a Salesforce Field Service (SFS) mobile app session timeout is configured (for example, 4 hours of inactivity), some users may observe that they remain logged in for 2–3 days or longer, even when no visible interaction with the app occurs. This behavior is Working As Designed (WAD). The SFS mobile app periodically calls backend APIs — such as Service Appointment list updates — based on the 'Schedule Update Frequency in Minutes' setting in Field Service Mobile Settings. These background API calls reset the session inactivity timer, preventing the session from expiring. As long as the app remains in the device's recent apps list (but not fully closed), background sync activity continues and the session stays active.