Overview
Transfer only the files that satisfy the configured selection criteria to one destination device at each run of a recurring schedule. Each run is intended to carry the matching subset rather than the whole source location.
Combine recurring execution with file selection criteria to deliver matching files to one destination device.
When should it start?
You can add more than one action.
What should happen after the transfer?
Select a development language to generate sample code for this configuration.
You can download the complete sample code for the configuration set above.
Apply the downloaded code and explore more examples.
AI-FRIENDLY EXPLANATION
This page shows how to send only the files that meet a selection rule to a single destination device on a recurring schedule. 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.
Transfer only the files that satisfy the configured selection criteria to one destination device at each run of a recurring schedule. Each run is intended to carry the matching subset rather than the whole source location.
Use this solution when a repeating delivery should carry only the files a rule picks out, which suits source folders that keep accumulating files of mixed types. The rule stays fixed while the schedule brings it back around.
COMMON QUESTIONS
Find answers to the most common questions about this configuration.
Configure the matching rules, destination, and recurrence using the supported builder options.
This depends on when files are discovered and selection criteria are evaluated. Confirm this behavior in the product documentation.
Check the matching criteria, source paths, file permissions, and execution logs.