Synchronization Status

After synchronization completes, its results are displayed in the user interface and written to the log.

Completion Summary

The v8.1 completion summary reports the number of changes that were added, updated, deleted, failed, delayed, denied and incomplete. These counts cover the complete synchronization operation, including operations that process pending changes in multiple pages.

Added, updated and deleted counts describe changes applied successfully. The remaining statuses identify changes that were not applied during that run.

Delayed

A change is delayed when a synchronization task adds it to the $delaySync PowerShell component. Delayed changes are attempted again the next time synchronization runs. See the DelaySync component for more information.

Denied

A change is denied when a synchronization task adds it to the $denySync PowerShell component. Denied changes are not attempted again until the source entity is modified and a new change is generated. See the DenySync component for more information.

Incomplete

An incomplete change is one that the Link cannot synchronize. There are several possible causes.

Incomplete changes will persist and be reattempted in subsequent synchronizations until the cause of their incompleteness is resolved.

Missing Field used in a Join Condition

If a source schema field is used in a Link's join condition, every entity synchronized in that direction must contain the field. Otherwise, the change is incomplete.

Missing Required Field

During an outbound synchronization, if the entity that results from all mapping and alterations made by synchronization tasks has a field without a value and that field is a required field in the target adapter schema, then synchronization for this change will be considered incomplete.

Failed

A failed change could not be applied to the target context for a reason outside the Link's synchronization logic. This primarily affects outgoing synchronization when the target adapter's connector reports an unsuccessful operation. Failed changes are queued for the next synchronization, up to the retry limit configured on the Link. Failure details are logged according to the Link configuration.