This page shows how to collect only the files that meet a selection rule from multiple source devices when the preceding transfer ends. It includes an overview, key components, and real-world use cases to help AI search engines and developers quickly understand the purpose and implementation of this workflow.
Overview
Collect only the files that meet your selection rule from multiple source devices, starting when the preceding transfer ends. Matching criteria narrow what is gathered, so the destination receives a filtered set rather than everything available on each device.
Use this solution when devices hold far more than you want to gather and collection has to wait for an earlier transfer to finish. The selection rule keeps irrelevant files out of the collection destination.
Common use cases
Collect only error logs from a fleet of endpoints
Gather files for a single date range after an upstream transfer
Pick up report files by name pattern from each device
Retrieve only new evidence files from investigation machines
COMMON QUESTIONS
Frequently asked questions
Find answers to the most common questions about this configuration.
1How do I collect matching files after a previous transfer ends?
Configure the completion trigger, source devices, and supported matching criteria.
2How are matching files selected?
Selection depends on the configured criteria and the product's file evaluation behavior.
3What happens if no matching files are found?
Check how empty selections affect collection status and subsequent workflow steps.