Mobile app offline sync fails after switching networks, causing data loss

BPM Microsoft Power Platform
, , , , , , , ,
1

We’re experiencing critical data loss with our Power Apps Mobile implementation. Field technicians using offline-enabled canvas apps report that unsaved records disappear when their devices switch between WiFi and cellular networks during work sessions.

The issue occurs most frequently when:

  • Users move from office WiFi to field (cellular)
  • Network handoff happens mid-form entry
  • App attempts to sync during network transition

Our current offline profile settings:


SyncInterval: 15 minutes
OfflineMode: Automatic
CacheSize: 500MB

We’ve verified the sync interval configuration is set to 15 minutes, but transitions seem to trigger immediate sync attempts that fail. The local cache retention appears inconsistent - sometimes data persists through network changes, other times it’s wiped completely.

Has anyone successfully configured network change handling in Power Apps Mobile to prevent this data loss? We need reliable offline sync that survives network transitions.

2

Good point about the app logic. Also verify your data source configuration - if you’re using Dataverse tables, make sure they’re properly marked for offline use with the correct sync scope. Tables not in the offline profile will always trigger online requests, which fail during network transitions and can cascade to affect properly configured tables.

3

You need to adjust your offline profile to use manual sync mode instead of automatic. Set OfflineMode: Manual and implement a custom sync button in your app. This prevents the OS network events from triggering sync operations. Also increase your cache retention timeout - 500MB size is fine but you need to set CacheRetentionDays: 7 to prevent premature cache clearing.

4

We’ve reviewed the app logic and found several OnVisible triggers that were polling connection status. Removed those and they were definitely contributing to the problem.

5

That makes sense - so the OS-level network event is forcing premature sync attempts. Is there a way to disable the automatic network-triggered sync while keeping the timed interval? Our users can tolerate the 15-minute delay but not the data loss.

6

I’ve seen this exact behavior. The automatic sync trigger on network change is actually a known issue with how Power Apps Mobile handles connection state transitions. Your 15-minute interval gets overridden when the OS reports network availability changes.

7

Another consideration: check your app’s OnStart and OnVisible properties. If you have any network status checks that trigger data refreshes, those will conflict with offline sync. I’ve seen apps that poll connection status and inadvertently clear local data when switching networks. The cache retention settings won’t help if your app logic is forcing refreshes.

8

Here’s the complete solution that addresses all four focus areas:

Offline Profile Settings: Switch from Automatic to Manual sync mode in your offline profile. This prevents OS-level network events from triggering sync operations:


OfflineMode: Manual
SyncInterval: 900000 (15 min in ms)

Sync Interval Configuration: Implement a custom sync button using the Power Apps Refresh() function tied to a timer control. Set the timer to 900000ms (15 minutes) and add a manual “Sync Now” button for user control. This gives you deterministic sync behavior independent of network state.

Local Cache Retention: Update your cache settings to prevent premature clearing:


CacheRetentionDays: 7
CacheSize: 500MB
PersistentCache: true

The PersistentCache: true flag is critical - it ensures data survives app restarts and network transitions.

Network Change Handling: Add network resilience logic to your app:

  1. Remove all OnVisible/OnStart connection status checks that trigger data operations
  2. Implement a connection check wrapper: `If(Connection.Connected, SyncData(), Notify(“Will sync when online”))
  3. Use the SaveData() and LoadData() functions to create an additional persistence layer for critical form data
  4. Add error handling to your sync operations: wrap sync calls in IfError() to catch network failures gracefully

Dataverse Table Configuration: Verify all tables used in your app are included in the offline profile with proper sync scope:

  • Navigate to Power Apps admin center → Offline Profile
  • Ensure all related tables are included (not just primary entities)
  • Set relationships to “Include related rows” for lookup fields
  • Test the profile in the mobile app using Settings → Offline Status

Additional Recommendations:

  • Enable diagnostic logging in the mobile app (Settings → About → Enable diagnostic logs) to capture sync failures
  • Implement optimistic concurrency handling for conflict resolution when sync eventually succeeds
  • Consider using the Power Apps component framework to build a custom offline status indicator that shows pending changes
  • Train users to manually sync before entering areas with known connectivity issues

This configuration has resolved the data loss issue for multiple clients. The key is preventing automatic sync triggers while maintaining reliable timed sync and persistent local storage. Test thoroughly with airplane mode toggles to simulate network transitions.