Sync Log
View the sync log summary
The sync log summary shows if a sync succeeded, failed, cancelled, or is currently running.
To view the sync log summary:
- On the Daspire sidebar navigation, click Dashboard.
- The Connections page displays.
- Click a connection in the list to view its sync history.
- Under Sync History, a list of syncs for that connection is displayed.
- The sync status is displayed (Succeeded, Cancelled, Failed, or Running) along with the summary of the sync log.
- For more information about a sync, click the sync log dropdown.
Sync log summary
Succeeded
The log summary for a successful sync shows the following data.
| Log | Description |
|---|---|
| x GB (also measured in KB, MB) | Amount of data moved during the sync. If basic normalization is on, the amount of data would not change since normalization occurs in the destination. |
| x emitted records | Number of records read from the source during the sync. |
| x committed records | Number of records the destination confirmed it received. |
| xh xm xs | Total time (hours, minutes, seconds) for the sync and basic normalization, if enabled, to complete. |
| Sync or Reset | The action that was performed (either a sync or a reset). |
NOTE: In a successful sync, the number of emitted records and committed records should be the same.
For Native syncs, per-stream emitted bytes describe data read from the source, while committed bytes describe the destination's confirmed write. Serialization can make these byte counts differ even when all records were transferred.
Cancelled
The log summary for a cancelled sync may show the following data.
| Log | Description |
|---|---|
| NaN Bytes | Since the sync was cancelled, the log does not show how much data was moved before cancelling. |
| No records | Since the sync was cancelled, the log does not show emitted or committed records. |
| xh xm xs | Total time (hours, minutes, seconds) between the beginning of sync and when it was cancelled. |
| Sync or Reset | The action that was performed (either a sync or a reset). |
| Failure Origin | The cause of the sync cancellation. |
NOTE: Daspire will try to sync your data three times. After a third failure, it will stop attempting to sync.
Failed
The log summary for a failed sync may show the following data.
| Log | Description |
|---|---|
| NaN Bytes | Since the sync failed, the amount of data is zero. |
| No records | Since the sync failed, there are no emitted or committed records. |
| xh xm xs | Total time (hours, minutes, seconds) between the beginning of the sync and when it failed. |
| Sync or Reset | The action that was performed (either a sync or a reset). |
| Failure Origin | The cause of the sync failure. |
Running
The sync log summary displays Running when the sync is actively running.
Skipped scheduled runs
The connection list may show Last skipped run under its schedule. Hover over it to see the scheduled time and reason: another sync was active, or a recovery sync covered that occurrence. This is historical information and can remain after a later successful sync. A skipped occurrence does not create another job or a catch-up run and does not change the current sync result. Older occurrences may have no recorded reason.
Enabled schedules waiting for an original commit
An enabled Native schedule can show Broken / Enabled · blocked while the platform verifies an earlier destination commit. The latest sync result is separate: an ordinary failed sync does not itself mean that future appointments are blocked. The connection's Status page explains why scheduled syncs are paused, how long they have been paused, how many scheduled syncs for this block have been skipped so far and whether the confirmation needs review by the Daspire team. Scheduled syncs resume automatically.
A confirmed commit can still be blocked while its original receipt, checkpoint and usage are being completed. This does not submit another destination write. Every blocked due appointment has its own historical record and retains its original scheduled time. Once the original protection is safely released, the next natural appointment resumes; saving again or running Sync Now is unnecessary.
After the block clears, the Status page shows a one-line summary of the scheduled syncs skipped during the last 72 hours, for example “8 scheduled syncs were skipped between 10/21/26, 6:24 AM and 10/21/26, 1:24 PM while the previous sync's write to the destination was being confirmed.” Skipped scheduled syncs are not new sync jobs, so they do not appear in the sync history, and the latest sync job keeps its original date. Scheduled syncs that were skipped only because the previous sync was still running are normal and are not listed.
The platform retains only the most recent twelve skipped appointments. When more
may have been skipped, the page says “At least 12 scheduled syncs…”. The
retained records, including original commit identifiers, are available through
nativeScheduleBlockedOccurrences in the connection status API.