CONDITIONAL FLOW EXECUTION
Control the next step of every transfer with conditions
Start transfers when a file is created, at a scheduled time or when a previous stage completes. Run only the stages whose conditions are met, decide the next job by each device's result, and recover interrupted transfers by the policy you set.
TRIGGERS & SCHEDULES
Start conditions — run transfers exactly when you want
Start automatically when a file arrives or a set time comes.
Use conditions such as a new file, a completed job or a scheduled time as the starting point of a transfer.
Automate everything from work that repeats hourly, daily, weekly or monthly to jobs that run when a specific event happens.
- Date / TimeDaily, 02:00 AM
- File EventNew File Created
- After TransferPrevious Step Completed
CONDITIONAL BRANCHING
Conditional branching — different work for different results
Not every result needs the same handling.
Separate follow-up work by results such as transfer success or failure and whether each target completed.
Completed targets move on to the next stage, while targets with problems wait or recover.
EXECUTION CONTROL
Execution control — parallel runs and concurrency policy
Run many transfers at once, but keep their scope under control.
Distribute files to many devices at once, and start with the targets that are ready to run. Control how many jobs run at the same time and whether duplicate runs are allowed, to build an operating policy that fits your devices and network.
CONCURRENT LIMIT4 / 20
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
New run request, duplicate policyQueued
EXECUTION WINDOWS & CONFLICTS
Time windows and run conflicts — keep your operating policy
Run in allowed hours, and handle overlapping jobs by policy.
Set the window in which transfers may run, and decide what happens when a new run is requested before the previous one has finished.
Even when several transfers to the same target overlap, a defined policy such as waiting, running in sequence or preventing duplicates applies.
ALLOWED TIME02:00 — 05:00
00:0006:00
EXECUTION QUEUE
Transfer ACompleted
Transfer BRunning
Previous run finished, started in orderRECOVERY POLICIES
Execution control on failure — wait, retry, recover
When something goes wrong, recover the way you set it up.
Set a handling policy for each situation, such as a dropped network, an offline device or full storage.
Files and stages that are already complete are kept, and only the targets with a problem wait or retry.
- Connection LostDevice 08, Network ErrorError
- Waiting for ConnectionReconnect PendingWait
- Transfer ResumedResume from Last PositionRetry
Recovery Progress100%
EXECUTION RESULTS
Execution results — see how conditions were actually applied
See which condition started a run, and why it waited or failed.
Check the Flow's run results and the status of each stage, and find the cause of an unmet condition, a retry, a wait or a failure.
Connect your run policies to actual results to improve the next round of settings.
RUN IDRUN-2026-018
| STEP | STATUS | TIME |
|---|---|---|
| TransferStarted by schedule, 02:00 | Done | 02:03 |
| RecoveryDevice 08 waited, reconnected | Done | 02:08 |
| CollectionRan after recovery | Done | 02:10 |
FREQUENTLY ASKED QUESTIONS
Conditions, branching and execution control,
frequently asked questions
Can a transfer start automatically when a file is created?
Yes. Set an event such as a new file being created as the start condition, and the Flow runs automatically.
Can I run transfers at a set time every day or every week?
Scheduled runs can be set up hourly, daily, weekly or monthly.
Can the next job run differently depending on the previous stage's results?
You can design follow-up conditions based on whether a stage completed and on each target's result. The exact branching range depends on the condition types the Flow supports.
Can transfers to many devices run at the same time?
Configure parallel transfers to many targets and run them within the supported concurrency range.
What happens if a new run is requested before the previous one has finished?
You can design a conflict policy, such as preventing duplicate runs or making them wait.
Can I allow transfers only at certain times?
Set an allowed transfer window and restrict runs outside it.
If some devices fail, do the other devices stop too?
Depending on the policy, healthy devices keep transferring while only the failed devices wait or retry.
Can I see run conditions and the causes of failures?
Runs shows each stage's result and error status. How much condition-evaluation history is shown depends on the logging that is implemented.
GET STARTED
Manage complex transfer conditions and run policies
in one Flow.
Build automation that fits your work, from start conditions to branching, concurrent runs and failure recovery.