Intelligence on the Edge
In 2026, Offline Edge Profiles enable agents to continue functioning without a network connection. This is critical for field workers in construction, healthcare, and remote infrastructure who operate in environments with intermittent or zero connectivity.
Architecture of an Offline Agent
An offline agent consists of three runtime layers:
- Local SLM (Small Language Model): A compressed, quantized model (e.g., Phi-3, Orca-Mini) cached on the device. It handles basic reasoning, form validation, and conversational guidance without any cloud dependency.
- Dataverse Delta Cache: A local SQLite mirror of the user's most relevant Dataverse records. Only records matching the user's 'Work Profile' (role + active projects) are synced, minimizing storage.
- Device-Side Automation Engine: Power Automate logic compiled into a JavaScript runtime within the mobile app wrapper. Simple flows (approvals, notifications, field updates) execute locally and queue cloud actions for later sync.
Conflict Resolution on Reconnect
When the device reconnects, a Delta Sync process begins:
- Timestamp Comparison: Each offline record carries a modification timestamp.
- Conflict Detection: If the same record was modified both locally and in the cloud, the system flags it.
- Resolution Strategy: Configurable per-table: 'Last Write Wins', 'Cloud Priority', or 'User Decision' (prompts the user to choose).
Background Sync Policies
| Policy | Behavior | Use Case |
|---|
| Aggressive | Sync every 30 seconds when connected | Real-time field data (safety inspections) |
| Balanced | Sync every 5 minutes, or on app resume | Standard field work |
| Battery Saver | Sync only on Wi-Fi or manual trigger | Remote sites with limited power |
🎯 Pro Tip: Always test your offline agent by enabling Airplane Mode on the device. The #1 cause of field failures is assuming that cached data is sufficient — ensure your Work Profile captures all necessary lookup tables, not just the primary entity.