This page shows how to collect files that meet a selection rule from multiple source devices when the preceding transfer ends and run follow-up actions after collection completes. 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 files matching your selection rule from multiple source devices when the preceding transfer ends, and run configured actions once collection completes. Filtering, sequencing, and post-collection work are described by a single workflow.
Key components
Multiple source devices and a collection destination
Use this solution for filtered gathering that has to sit behind an earlier transfer and feed something afterwards, such as an indexing step, a notification, or a backup copy. It avoids stitching the selection rule, the trigger, and the post-processing together by hand.
Common use cases
Index collected audit files after each gathering run
Alert reviewers when matching evidence files arrive
Feed filtered log sets into an analysis job
Copy selected device reports into a compliance archive
COMMON QUESTIONS
Frequently asked questions
Find answers to the most common questions about this configuration.
1How do I chain matching-file collection with follow-up actions?
Configure the completion trigger, matching rules, source devices, and supported actions.
2Do follow-up actions run if one source fails?
Verify whether actions depend on overall completion, individual source results, or another configured condition.
3How do I investigate incomplete collection?
Review the preceding transfer, matching criteria, source-level results, and logs.