Defines how we propagate a file when it has changed on both sides and the latest edition cannot be automatically determined. By default the selection for this setting is "Conflict Copy" however there are 4 additional settings beyond this which have been gone into greater detail below. Your selection will depend on what best fits your business needs.

Conflict Copy (Default Selection):

When a conflict is detected for a file on both the Source and the Destination, Conflict Copy will identify the versions for the file and append a time-stamp to preserve the integrity of each. We will make a copy of the earliest version then override the content with the latest.

Expand for more information

Based on your transfer type selected, you can expected the following behavior for Conflict Copy

Synchronize - Will always prefer the latest version and put the Conflict Copy on the side that is the earliest

Copy - Will always prefer the version located on the Source and put the conflict copy on the Destination

Migrate - Conflict Copy Policy is not applicable. With transfer type Migrate, SkySync will always prefer the Source. Also, since SkySync does not run change detection on subsequent job runs for Migrate, conflict policy would not be applicable

Publish - Conflict Copy Policy is not applicable. With transfer type Publish, SkySync will always prefer the Source; regardless of conflict

Taxonomy - Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, conflict policy would not be applicable

Prefer Latest:

When a conflict is detected for a file on both the Source and the Destination, Prefer Latest will identify the versions for the file and override the content with the latest version

Expand for more information

Based on your transfer type selected, you can expected the following behavior for Prefer Latest Policy:

Synchronize - If the latest version is on the Source, SkySync will transfer from the Source and override the Destination with the latest version. If the latest version is on the Destination, SkySync will transfer from the Destination and override the Source with the latest version

Copy - If the latest version is on the Source, SkySync will transfer from the Source and override the Destination with the latest version. If the latest version is on the Destination, SkySync will skip the file for transfer and flag with a "Not Allowed" failure in the log.

Migrate - Prefer Latest Conflict Policy is not applicable. With transfer type Migrate, SkySync will always prefer the Source. Also, since SkySync does not run change detectionon subsequent job runs for Migrate, Prefer Latest Conflict Policy would not be applicable

Publish - Prefer Latest Conflict Policy is not applicable. With transfer type Publish, SkySync will always prefer the Source; regardless of conflict

Taxonomy - Prefer Latest Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Prefer Latest Conflict Policy would not be applicable

Prefer Source:

When a conflict is detected for a file on both the Source and the Destination, the Destination will always be overridden; regardless of version.

Expand for more information

Based on your transfer type selected, you can expected the following behavior for Prefer Source Policy:

Synchronize - Will always transfer from the Source and override on the Destination; regardless of which version is later

Copy - Will always transfer from the Source and override on the Destination; regardless of which version is later

Migrate: Prefer Source Conflict Policy is not applicable. With transfer type Migrate, SkySync will always prefer the Source. Also, since SkySync does not run change detection on subsequent job runs for Migrate, Prefer Source Conflict Policy would not be applicable

Publish - Prefer Source Conflict Policy is not applicable. With transfer type Publish SkySync will always prefer the Source; regardless of conflict

Taxonomy - Prefer Source Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Prefer Source Conflict Policy would not be applicable

Prefer Destination:

When a conflict is detected for a file on both the Source and the Destination, the Source will always be overridden; regardless of version.

Expand for more information

Based on your transfer type selected, you can expected the following behavior for Prefer Destination Policy:

Synchronize - Will always transfer from the Destination and override on the Source; regardless of which version is later

Copy - Will always transfer from the Destination and override on the Source; regardless of which version is later

Migrate: Prefer Desintation Conflict Policy is not applicable. With transfer type Migrate, SkySync will always prefer the Source. Also, since SkySync does not run change detection on subsequent job runs for Migrate, Prefer Destination Conflict Policy would not be applicable

Publish - Prefer Destination Conflict Policy is not applicable. With transfer type Publish, SkySync will always prefer the Source; regardless of conflict

Taxonomy - Prefer Destination Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Prefer Destination Conflict Policy would not be applicable

Failure:

When a conflict is detected for a file on both the Source and the Destination, Failure will flag the file and log it. The conflict file will be skipped and no changes will occur.

Expand for more information

Based on your transfer type selected, you can expected the following behavior for Failure Policy:

Synchronize - If SkySync detects a conflict, it will be flagged and logged as failure. The conflict file will be skipped and no changes will occur

Copy - If SkySync detects a conflict, it will be flagged and logged as failure. The conflict file will be skipped and no changes will occur

Migrate- Failure Conflict Policy is not applicable. With transfer type Migrate, SkySync will always prefer the Source. Also, since SkySync does not run change detection on subsequent job runs for Migrate, Failure Conflict Policy would not be applicable

Publish - Failure Conflict Policy is not applicable. With transfer type Publish, SkySync will always prefer the Source; regardless of conflict

Taxonomy - Failure Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Failure Conflict Policy would not be applicable

Conflict Resolution

Conflict Copy (Default Selection):

When a conflict is detected for a file on both the Source and the Destination, Conflict Copy will identify the versions for the file and append a time-stamp to preserve the integrity of each. We will make a copy of the earliest version then override the content with the latest.

Based on your transfer type selected, you can expected the following behavior for Conflict Copy

Synchronize - Will always prefer the latest version and put the Conflict Copy on the side that is the earliest

Copy - Will always prefer the version located on the Source and put the conflict copy on the Destination

Migrate - Conflict Copy Policy is not applicable. With transfer type Migrate, SkySync will always prefer the Source. Also, since SkySync does not run change detection on subsequent job runs for Migrate, conflict policy would not be applicable

Publish - Conflict Copy Policy is not applicable. With transfer type Publish, SkySync will always prefer the Source; regardless of conflict

Taxonomy - Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, conflict policy would not be applicable

Prefer Latest:

When a conflict is detected for a file on both the Source and the Destination, Prefer Latest will identify the versions for the file and override the content with the latest version

Based on your transfer type selected, you can expected the following behavior for Prefer Latest Policy:

Synchronize - If the latest version is on the Source, SkySync will transfer from the Source and override the Destination with the latest version. If the latest version is on the Destination, SkySync will transfer from the Destination and override the Source with the latest version

Copy - If the latest version is on the Source, SkySync will transfer from the Source and override the Destination with the latest version. If the latest version is on the Destination, SkySync will skip the file for transfer and flag with a "Not Allowed" failure in the log.

Migrate - Prefer Latest Conflict Policy is not applicable. With transfer type Migrate, SkySync will always prefer the Source. Also, since SkySync does not run change detectionon subsequent job runs for Migrate, Prefer Latest Conflict Policy would not be applicable

Publish - Prefer Latest Conflict Policy is not applicable. With transfer type Publish, SkySync will always prefer the Source; regardless of conflict

Taxonomy - Prefer Latest Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Prefer Latest Conflict Policy would not be applicable

Prefer Source:

When a conflict is detected for a file on both the Source and the Destination, the Destination will always be overridden; regardless of version.

Based on your transfer type selected, you can expected the following behavior for Prefer Source Policy:

Synchronize - Will always transfer from the Source and override on the Destination; regardless of which version is later

Copy - Will always transfer from the Source and override on the Destination; regardless of which version is later

Migrate: Prefer Source Conflict Policy is not applicable. With transfer type Migrate, SkySync will always prefer the Source. Also, since SkySync does not run change detection on subsequent job runs for Migrate, Prefer Source Conflict Policy would not be applicable

Publish - Prefer Source Conflict Policy is not applicable. With transfer type Publish SkySync will always prefer the Source; regardless of conflict

Taxonomy - Prefer Source Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Prefer Source Conflict Policy would not be applicable

Prefer Destination:

When a conflict is detected for a file on both the Source and the Destination, the Source will always be overridden; regardless of version.

Based on your transfer type selected, you can expected the following behavior for Prefer Destination Policy:

Synchronize - Will always transfer from the Destination and override on the Source; regardless of which version is later

Copy - Will always transfer from the Destination and override on the Source; regardless of which version is later

Migrate: Prefer Desintation Conflict Policy is not applicable. With transfer type Migrate, SkySync will always prefer the Source. Also, since SkySync does not run change detection on subsequent job runs for Migrate, Prefer Destination Conflict Policy would not be applicable

Publish - Prefer Destination Conflict Policy is not applicable. With transfer type Publish, SkySync will always prefer the Source; regardless of conflict

Taxonomy - Prefer Destination Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Prefer Destination Conflict Policy would not be applicable

Failure:

When a conflict is detected for a file on both the Source and the Destination, Failure will flag the file and log it. The conflict file will be skipped and no changes will occur.

Based on your transfer type selected, you can expected the following behavior for Failure Policy:

Synchronize - If SkySync detects a conflict, it will be flagged and logged as failure. The conflict file will be skipped and no changes will occur

Copy - If SkySync detects a conflict, it will be flagged and logged as failure. The conflict file will be skipped and no changes will occur

Migrate- Failure Conflict Policy is not applicable. With transfer type Migrate, SkySync will always prefer the Source. Also, since SkySync does not run change detection on subsequent job runs for Migrate, Failure Conflict Policy would not be applicable

Publish - Failure Conflict Policy is not applicable. With transfer type Publish, SkySync will always prefer the Source; regardless of conflict

Taxonomy - Failure Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Failure Conflict Policy would not be applicable