This page shows how to send files that meet configured selection criteria from one source device to multiple destination devices on a recurring schedule and run follow-up actions after the transfer 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
Run a recurring distribution that carries only the files meeting configured matching criteria to multiple destination devices, and perform additional tasks after the transfer completes. Selection rules, recurrence, and post-transfer actions are configured together as one workflow.
Key components
Source device with file selection criteria
Multiple destination devices
Recurring schedule
Follow-up actions (after transfer)
How it fits your workflow
Use this solution for a repeating pipeline where a filtered delivery has to be followed by processing, such as loading the delivered files, archiving the originals, or alerting the owning team. It replaces a chain of separate scripts for selection, scheduling, delivery, and follow-up.
Common use cases
Pick up matching exports each hour, deliver them, and start a load job
Distribute filtered firmware packages and run an install script
Send matching invoice files to multiple systems and archive the originals
Deliver selected data files and post a completion notice to a channel
COMMON QUESTIONS
Frequently asked questions
Find answers to the most common questions about this configuration.
1How do I automate recurring matching-file distribution with follow-up actions?
Set the matching rules and recurrence, configure the destinations, and enable supported actions.
2What happens if only some destinations receive the files?
Check the documented completion criteria and per-destination failure behavior.
3How can I verify each recurring execution?
Review execution records, transfer results, and follow-up action status.