This page shows how to send files that meet configured selection criteria from one source device to multiple destination devices 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.
Overview
Repeatedly transfer the files that meet configured matching criteria to multiple destination devices on a recurring schedule. Each run works from the selection rules rather than a fixed file list, so what a run contains depends on which files match when it is evaluated.
Key components
Source device (e.g., Windows)
Multiple destination devices
File selection criteria (e.g., name pattern or extension)
Recurring schedule
How it fits your workflow
Use this solution when a repeating distribution should carry only part of what sits on the source, such as files of a given type or naming pattern, instead of an entire folder. The rules are configured once and applied to every recurring run.
Common use cases
Send new CSV exports to multiple analytics servers each hour
Distribute files matching a naming convention to regional offices weekly
Push only image and media files to several content endpoints
Forward daily log files to multiple collection hosts
COMMON QUESTIONS
Frequently asked questions
Find answers to the most common questions about this configuration.
1How do I send matching files to multiple devices on a recurring schedule?
Configure the matching criteria and destination devices, then set the recurrence.
2Can newly added files be included in future runs?
Confirm how the product discovers files and evaluates matching criteria for each execution.
3How do I troubleshoot skipped files?
Review selection rules, source paths, file access, and transfer logs.