MULTI-STAGE FLOW DESIGN
Distribute, collect, and deliver again.
Design it all as one Flow.
Connect server-to-server transfers, distribution to many devices and per-device result collection in one Multi-Stage Flow. Set the order, start conditions and failure handling of each stage, and automate complex file transfers.
Studio / FlowsCompleted
Multi-Stage Flow3 stages
COMPOSE TRANSFER STAGES
Combine the transfers you need,
stage by stage.
One Flow can hold a one-to-one transfer, distribution to many devices and collection from many devices together.
Give each stage its own source and destination, files to transfer and run conditions.
Design anything from a simple A→B→C transfer to a combined job that distributes files and then collects the results.
Flow Stages
- 01DeployCentralDevices20 targets
- 02CollectDevicesStorage20 sources
- 03TransferStorageAnalysis3 targets
EXECUTION CONDITIONS
Start the next transfer
based on the previous stage.
Run follow-up stages on conditions such as a scheduled time, the completion of the previous stage or a new file being created.
Set the completion condition each stage needs, and the order of work is managed automatically.
Execution Rules
- Scheduled Start09:00 AM, DeployDone
- Deployment Completed20 / 20 devices
- Start CollectionAfter previous stageDone
- Collection Completed20 / 20 results
- Start TransferAfter previous stageDone
PARALLEL & CONDITIONAL EXECUTION
Transfer to many targets at once,
and decide what comes next by the results.
Distribute files to many devices at the same time, or run follow-up work according to each device's result.
Define the run policy your work needs, such as waiting for every target to finish or moving completed targets on to the next stage first.
Parallel Distribution
- 15Completed
- 4Running
- 1Failed
FAILURE HANDLING
Even if a stage fails,
keep the work that is already done.
When a transfer stops because the network drops, a device goes offline or storage runs out, it waits, retries or resumes according to the policy you set.
Completed stages are kept and only the failed stage or targets are recovered, which avoids unnecessary duplicate transfers.
Recovery Monitor
Deployment20 / 20 done
Device 20Completed
Resumed from 64%
Recovery policyResume
FLOW EXECUTION
Run the Flow you designed,
and check the results of each stage.
See the overall run status of the Flow in Studio, along with the target devices and transfer results of every stage.
When needed, look into the file history of a specific stage or device to analyze a problem.
Flow Results
- 01Deploy20 Devices
- 02Collect20 Results
Device 01, result.zip, 2.1 MBCompleted
- 03Transfer3 Targets
FREQUENTLY ASKED QUESTIONS
Multi-Stage Flow design,
frequently asked questions
What is a Multi-Stage Flow?
A way to connect several file transfers stage by stage inside one Flow and set the run order, conditions and failure handling policy.
Can distribution and collection go in the same Flow?
A combined transfer that distributes files to many devices and then collects the result files can be built as one Flow.
Can I transfer from A to B, and then from B to C?
Set the source and destination of each stage to build a multi-stage transfer such as A→B→C.
Does the next stage start only after the previous one finishes?
You can set up sequential runs, and design follow-up transfers to start on each stage's run and completion conditions.
Can I distribute to many devices at the same time?
One stage can be set up to distribute files to many target devices.
If only some devices fail, do I have to run the whole Flow again?
Under the recovery policy you set, completed work is kept and only the failed targets or stages are retried.
What happens if a device is offline or runs out of storage?
You can design a failure handling policy that fits the situation, such as waiting, retrying, resuming the transfer or skipping that target.
Can I see the results of each stage of a Flow run?
Runs in Studio shows the overall Flow status and the transfer results by stage and by device.
GET STARTED
Design many transfers as one Flow.
Combine distribution, collection and server-to-server transfers, and set up run conditions and failure handling yourself.