Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Migrations
  • Flagged Items

Ignored Filter Reasons

Learn the meaning of the different ignored status values.

Written by Andrea Harvey

Updated at May 16th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Insights
    Prebuilt Insights Custom Insights
  • Content
  • Accounts
  • Activity Log
  • Content Scans
  • Migrations
    Migration Jobs Migration Reports Maps Flagged Items Migration Tools
  • Connections
    Supported Platform Connections Creating Connections Connection Maintenance Connection Pools
  • Entity Types
    DryvIQ Available Entity Types Custom Entity Types Entity Type Maintenance
  • Action Sets
    Creating Action Sets Action Sets Maintenance
  • Settings
    License Performance Notifications Extensions Entity Types Settings Display Settings Configuration
  • API, CLI, and SDK Documentation
    REST API Documentation Command-line Interface SDK Development
  • POC Offering
  • Release Notes
+ More

Table of Contents

Overview Ignored Categories

Overview

DryvIQ tracks why items were categorized as ignored/skipped by policy as configured during job creation. These categories are used in the Job Validation Report. Ignored reasons are also available on the items grid by filtering the list by the “Ignored” status and selecting one of the ignored reason categories.

Ignored Categories

Reason Description
Content extension The item was ignored due to a third-party extension. This filter can only be set through the REST API. 
Date The item was ignored due to a date range filter. The created on, modified on, or last touched date falls within the specified date range. 
Empty container policy The item was ignored because the Empty Container policy is set to skip empty folders.
File extensions The item was ignored due to a file extension filter.  
Hidden The item was ignored because the job is set to ignore hidden items. 
Item type The item was ignored due to a file type filter.
Large item policy The item was ignored due to the Large Item policy. The file is too large to be transferred to the destination platform.
match fail The item was ignored due to an error while calculating a destination path.
metadata The item was ignored due to a metadata filter. 
Destination items only The item was ignored because the Item Inspection policy is set to None. All existing content in the destination root is tracked as destination-only items and reported as ignored. This applies to jobs configured to transfer in one direction (source to destination only). 
Oerwrite policy The item was ignored because the Item Overwrite policy is set to skip files with the same name as files on the destination platform. 
Path The item was ignored due to a path filter. 
Pattern The item was ignored due to a name pattern filter.
Predefined The item was ignored due to the predefined content categories filter. 
Restricted content policy The item was ignored due to the restricted content policy.
Shared The item was ignored due to the shared items filter.
Size The item was ignored due to a file size filter.
Unknown filter reason The item was ignored for an unknown reason. This includes items ignored by previous DryvIQ versions on upgraded installations.

 

flagged ignored validation skipped

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Has External Permissions (REST API Only)
  • Length Exceeds Function (REST API Only)
  • Duplicate Name Policy Using REST API

Copyright 2025 – DryvIQ.

Knowledge Base Software powered by Helpjuice

Expand