File Version Conflicts Job Policy

Learn how to configure how DryvIQ handles version conflicts.

Updated at May 22nd, 2025

+ More

Table of Contents

Overview Keep Both Files Prefer Most Recently Modified File Prefer the Version on Source Prefer the version on the Destination Flag the File

Overview

The File Version Conflicts job policy determines how DryvIQ will behave when a file version conflict is detected on the source or the destination. There are five options, but not every option applies depending on the transfer direction selected. Refer to the information below to understand how the different transfer types handle each version conflict policy option.

Keep Both Files

This is referred to as Conflict Copy and is the default conflict policy. When a file changes on both the source and the destination, DryvIQ will identify the files' versions and append a timestamp to preserve the integrity of each. It will make a copy of the earliest version and override the content with the latest. You can expect the following behavior for the Conflict Copy policy based on the transfer direction selected for the job.

Transfer Type	Behavior
Synchronize	Will always prefer the latest version and put the Conflict Copy on the side with the earliest timestamp. Using this setting for a sync job will result in duplicate copies of files. Therefore, for sync jobs, the “Prefer Most Recently Modified File” is the preferred setting.
Copy	Will always prefer the version located on the source and puts the conflict copy on the destination.
Migrate	Conflict Copy Policy is not applicable. With transfer type Migrate, the application will always prefer the source. Also, since the application does not run change detection on subsequent job runs for Migrate, the conflict policy would not be applicable.
Publish	Conflict Copy Policy is not applicable. With transfer type Publish, the application will always prefer the source, regardless of conflict.
Move	Conflict Copy Policy is not applicable. With transfer type Move, the application will always prefer the latest version. Also, since the application does not run change detection on subsequent job runs with Move, conflict policy would not be applicable.
Copy Folder Structure	Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, conflict policy would not be applicable.

Prefer Most Recently Modified File

This policy prefers the latest version. When a file changes on both the source and the destination, DryvIQ will identify the file's latest version and override the content with the latest. You can expect the following behavior for the Prefer Latest policy based on the transfer direction selected for the job.

Transfer Type	Behavior
Synchronize	If the latest version is on the source, the application will transfer from the source and override the destination with the latest version. If the latest version is on the destination, the application will transfer from the destination and override the source with the latest version
Copy	If the latest version is on the source, the application will transfer from the source and override the destination with the latest version. If the latest version is on the destination, the application 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, the application will always prefer the source. Also, since the application does not run change detection on subsequent job runs for Migrate, the Prefer Latest conflict policy would not be applicable.
Publish	Prefer Latest Conflict Policy is not applicable. With transfer type Publish, the application will always prefer the source, regardless of conflict.
Move	Prefer Latest Conflict Policy is not applicable. With transfer type Move, the application will always prefer the latest version. Also, since the application does not run change detection on subsequent job runs with Move, the Prefer Latest conflict policy would not be applicable.
Copy Folder Structure	Prefer Latest Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, the Prefer Latest conflict policy would not be applicable.

Prefer the Version on Source

When a file changes on both the source and the destination, the destination copy will always be overridden, regardless of version. You can expect the following behavior for the Prefer Source policy based on the transfer direction selected for the job.

Transfer Type	Behavior
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, the application will always prefer the source. Also, since the application does not run change detection on subsequent job runs for Migrate, the Prefer Source conflict policy would not be applicable.
Publish	Prefer Source Conflict Policy is not applicable. With transfer type Publish the application will always prefer the source, regardless of conflict.
Move	Prefer Source Conflict Policy is not applicable. With transfer type Move, the application will always prefer the latest version. Also, since the application does not run change detection on subsequent job runs with Move, the Prefer Source conflict policy would not be applicable.
Copy Folder Structure	Prefer Source Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, the Prefer Source conflict policy would not be applicable.

Prefer the version on the Destination

When a file changes on both the source and the destination, the source copy will always be overridden, regardless of version. You can expect the following behavior for the Prefer Destination policy based on the transfer direction selected for the job.

Transfer Type	Behavior
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 Destination Conflict Policy is not applicable. With transfer type Migrate, the application will always prefer the source. Also, since the application does not run change detection on subsequent job runs for Migrate, the Prefer Destination conflict policy would not be applicable.
Publish	Prefer Destination Conflict Policy is not applicable. With transfer type Publish, the application will always prefer the source regardless of conflict.
Move	Prefer Destination Conflict Policy is not applicable. With transfer type Move, the application will always prefer the latest version. Also, since the application does not run change detection on subsequent job runs with Move, the Prefer Destination conflict policy would not be applicable.
Copy Folder Structure	Prefer Destination Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, the Prefer Destination conflict policy would not be applicable.

Flag the File

When a file changes 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. You can expect the following behavior for the Failure policy based on the transfer direction selected for the job.

Transfer Type	Behavior
Synchronize	If the application detects a conflict, it will be flagged and logged as a failure. The conflict file will be skipped, and no changes will occur.
Copy	If the application detects a conflict, it will be flagged and logged as a failure. The conflict file will be skipped, and no changes will occur.
Migrate	Failure Conflict Policy is not applicable. With transfer type Migrate, the application will always prefer the source. Also, since the application does not run change detection on subsequent job runs for Migrate, the Failure conflict policy would not be applicable.
Publish	Failure Conflict Policy is not applicable. With transfer type Publish, the application will always prefer the source, regardless of conflict.
Move	Failure Conflict Policy is not applicable. With transfer type Move, the application will always prefer the latest version. Also, since the application does not run change detection on subsequent job runs with Move, the Failure conflict policy would not be applicable.
Copy Folder Structure	Failure Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, the Failure conflict policy would not be applicable.

migrate migrations job file version version conflicts policy