Large Item Policy Using REST API
Learn how to manage the large item policy for migration jobs using the DryvIQ REST API.
Written by Andrea Harvey
Updated at May 2nd, 2025
Table of Contents
Overview
The Large Item policy determines DryvIQ's behavior when it encounters items that are too large to upload to a given platform. If you have content that may violate a platform's file size policy, DryvIQ recommends this policy.
You can use the job filters to filter content by size.
| Options | Behavior |
|---|---|
| "large_item": "fail" | Failed item will be reported as error in the transfer audit log. This is the default option. |
| "large_item": "skip" | The file will be skipped/ignored and an informational activity logged. In the database, this will be in the transfer items table with a status item value of 5. In the UI Log Report, the message will state “The item was too large to transfer into the destination storage platform: /….” |
Job JSON Example
{
"name":"Simple Transfer Job with Large Item Policy",
"kind": "transfer",
"transfer": {
"large_item": "skip",
"transfer_type": "copy",
"source": {
"connection": { "id": "{{nfs_connection}}" },
"target": {
"path": "/SourcePath"
}
},
"destination": {
"connection": { "id": "{{cloud_connection}}" },
"target": {
"path": "/DestinationPath"
}
}
},
"schedule": {
"mode": "manual"
}
}