Common Sync Errors
Synchronization can fail for various reasons. Check the Run History for error details and use this guide to resolve common issues:
| Error Type | Cause and Solution |
| Timeout during extraction | Large tables may timeout on initial sync. Data Mission Sync will automatically resume from where it left off. Allow the sync to retry. |
| Change tracking not enabled | The table requires change tracking. Enable it in Power Platform Admin Center or make.powerapps.com → Tables → Properties → Track changes. |
| Rate limit exceeded | Dataverse API limits were hit. Data Mission Sync automatically backs off and retries. For very large syncs, this may extend the sync duration. |
| Schema mismatch | A column in Dataverse changed type in a way that conflicts with the target. Contact support for assistance with schema evolution. |
| Connection lost mid-sync | Network interruption occurred. The sync will automatically retry. Check your Azure SQL database is accessible. |
| Insufficient database space | Your Azure SQL database is full. Increase the database size or clean up old data. |
Interpreting Run History Status
Each sync run in Run History shows a status that indicates what happened:
| Status | Meaning |
| Successful | The sync completed without errors. All data was transferred successfully. |
| Failed | The sync encountered an error. Click on the run to see error details. |
| In Progress | The sync is currently running. Large initial syncs may take several minutes. |
| Extracting | Data is being pulled from Dataverse. This phase queries the source system. |
| Skipped | No changes detected since the last sync. This is normal and efficient. |
Recovering from Failed Syncs
Data Mission Sync is designed to recover automatically from most failures:
• Automatic Retry: Failed syncs are automatically retried on the next scheduled run
• Incremental Recovery: Syncs resume from the last successful checkpoint, not from the beginning
• Transient Error Handling: Network blips, rate limits, and timeouts are handled with exponential backoff
If a sync continues to fail after multiple attempts:
1. Check Run History for specific error messages
2. Verify your source and target connections are still valid (use Test Connection)
3. Check that your App Registration secret hasn't expired
4. Ensure your Azure SQL firewall still allows the Data Mission Sync IP
5. For persistent issues, use Reset + Full Sync to clear watermarks and start fresh
| ⚠ Warning: Reset + Full Sync re-copies all data and may take significant time for large tables. Use only when incremental sync cannot recover. |