Overview

This job policy determines how DryvIQ will behave when a file version conflict is detected on either the source or the destination. This policy is applied only during subsequent (delta) job runs; it does not execute during the initial job run, since the destination is expected to be empty or not yet in conflict.

Keep Both Files

This is also referred to as a Conflict Copy. When a file changes on both the source and the destination, DryvIQ will identify the file's versions and append a timestamp to preserve each version's integrity. We will make a copy of the earliest version and override the content with the latest. This is the default conflict policy.

Based on the transfer type selected for the job, you can expected the following behavior for Conflict Copy Policy.

Transfer Type	Behavior

Transfer Type	Behavior
Synchronize	Will always prefer the latest version and put the Conflict Copy on the side that is the earliest. Using this setting for a sync job will result in duplicate copies of files. Therefore, for sync jobs, the “Prefer Most Recently Modified File” setting is preferred.
Copy	Will always prefer the version in the source and place the conflict copy in 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 the transfer type Publish, the application will always prefer the source, even in the presence of a 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, the conflict policy would not be applicable.
Copy Folder Structure	Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, the 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 latest version of the file and override its content with the latest version.

Based on the transfer type selected for the job, you can expect the following behavior for the Prefer Latest Policy.

Transfer Type	Behavior

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 log a "Not Allowed" failure.
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 the transfer type Publish, the application will always prefer the source, even in the presence of a 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.

Based on the transfer type selected for the job, you can expect the following behavior for the Prefer Source Policy.

Transfer Type	Behavior

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, Prefer Source Conflict Policy would not be applicable.

Prefer the Version on Destination

When a file changes on both the source and the Destination, the source copy will always be overridden regardless of version.

Based on the transfer type selected for the job, you can expect the following behavior for the Prefer destination Policy.

Transfer Type	Behavior

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 the transfer type Publish, the application will always prefer the source, even in the presence of a 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.

Based on the transfer type selected for the job, you can expect the following behavior for Failure Policy.

Transfer Type	Behavior

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. Manual remediation is required.
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. Manual remediation is required.
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, 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

Copy Conflict Using the REST API

Configuration options available in using the REST API correspond directly with the user interface options.

REST API Setting	UI Setting

REST API Setting	UI Setting
copy (This is the default option.)	Keep both files
latest	Prefer the most recently modified file
source	Prefer the version on the source
destination	Prefer the version on the destination
failure	Flag the file

POST {{url}}v1/jobs

{
  "name":"Conflict Policy Test",
  "kind": "transfer",
  "transfer": {
      "audit_level": "trace",
      "transfer_type": "copy",
      "conflict_resolution": "latest",
      "source": {
        "connection": { "id": "{{cloud_connection_source}}" },
        "target":
        {"path":"/SourcePath"}
      },
      "destination": {
        "connection": { "id": "{{cloud_connection_destination}}" },
        "target": {
          "path": "/DestinationPath"
        }
      }
  },
  "schedule": {
    "mode": "manual"
  }
}