Confirmed working: Offline status update sync resolved

oh nice thanks for confirming this sam i was wondering if it actually worked. did u do anything special on reconnect or did it just auto sync

nah just opened the app on wifi and let it sit for like 30 seconds. saw the little sync spinner do its thing and all my jobs updated. didn't have to hit any buttons or anything

in my experience this only works if you don't force close the app. kill it while offline and you're hosed

Pro tip: Art's right about that one — the queue lives in memory, so if you swipe away the app while offline those pending changes can get lost. I've trained my guys to just let the app sleep in background if they're in a dead zone.

Sam, glad it worked out for you. For anyone else reading, the full walkthrough is in this Help Center article on syncing when you reconnect.

see told ya. happened to me twice before i figured it out

Hi Sam, happy to help confirm this!

What you're describing is exactly how offline status updates are designed to work. Here's what's happening under the hood:

1. Status changes made offline are stored in a local queue
2. On reconnect, the app syncs automatically (you'll see the spinner Sam mentioned)
3. Conflicts are resolved server-side with timestamps

Important: Do not force-close the app while offline, as Art and Josh noted — this clears the queue. Backgrounding the app is fine.

We've also seen improved reliability with this flow in app version 3.2.1 and later. If anyone is still experiencing issues after following these steps, feel free to tag me and I can dig into your specific account.

Thanks for sharing this. For FieldPulse, I would first confirm that the mobile app has synced recently, then compare the work order status in the technician view with what dispatch sees. If those match, capturing the job number and last sync time will make it easier for support to trace the update.