Skip to main content

Offline Mode

Plantrunner's mobile app works offline, so field technicians can continue working even without internet access. Data is stored locally and synced automatically when connectivity returns.

What works offline​

  • Service visits -- Check in, log tasks, add notes, and check out
  • Route viewing -- See today's route and location details (if cached)
  • Timesheet entry -- Log hours worked
  • Data entry -- Form submissions are queued locally and synced when online

How offline sync works​

  1. When you perform an action offline (e.g., check in at a location), the data is saved to your device's local storage (IndexedDB)
  2. The action is added to a sync queue
  3. Plantrunner monitors your network status
  4. When internet connectivity returns, the sync queue is processed automatically
  5. Each queued action is sent to the server in order
  6. You receive confirmation when the sync is complete

Sync indicators​

The app shows visual indicators for sync status:

  • Synced -- Data has been successfully uploaded to the server
  • Pending sync -- Data is stored locally and waiting for connectivity
  • Sync in progress -- Currently uploading queued data

Photos​

Photos taken offline are stored locally on the device. They are uploaded when connectivity returns. Large photos may take longer to sync depending on your connection speed.

Data caching​

When you have internet access, Plantrunner caches data locally for offline use:

  • Customer and location information
  • Route details and waypoints
  • Employee data
  • Timesheet records

This cached data is available when you go offline, though it may become stale if changes were made on another device.

Best practices​

  • Open the app while online before heading into areas with poor connectivity. This ensures the latest data is cached
  • Don't worry about lost data -- The sync queue preserves all your entries. Nothing is lost when you go offline
  • Check sync status at the end of your day to confirm everything has been uploaded

Conflict handling​

If the same record is modified on both the device and the server while offline, the mobile version takes priority during sync. This is rare in normal usage since each technician typically only modifies their own visits.