FLOW OPERATIONS & ASSURANCE
Track every stage of a complex Flow,
and verify it all the way to success.
Monitor a Flow that combines distribution, collection and server-to-server transfers as one run. See progress and error and recovery history by stage, device and file, and use Assurance to verify the success conditions you defined in advance.
- Deployment100%Completed
- Collection100%Completed
- Transfer100%Completed
Device Progress20 Devices
- Device A100%
- Device B100%
- Device C100%
FLOW MONITORING
See every transfer stage
in one Flow.
Even when distribution, collection and server-to-server transfers are chained across several stages, you see their overall progress as one run.
Know which stages are complete, which are in progress, and what the next stage is waiting for.
FLOW RUNRUN-20481, 3 Stages
- DeploymentDone
- CollectionRunning
- Final TransferPending
DEVICE & FILE DETAILS
Find which file on which device
the transfer stopped at.
Select a stage and a device from the whole Flow to see the transfer history of each file.
Tell interrupted files apart from completed ones, and see how far each transfer got.
DEVICE FILESDevice C, Collection
Files2 items
result_002
- result_001.zipTransferCompleted
- result_002.zipTransferInterrupted
ASSURANCE CONTRACT
Sending the files and succeeding at the job
are not the same thing.
Even when the transfer itself succeeds, the job can still fail by business standards if it ran past the allowed time or missed some required targets.
Define basic success conditions and exception policies in an Assurance Contract, and verify that each run's results met them.
CONTRACT
SUCCESS CRITERIA
- Devices
- 20/20
- Integrity
- Verified
- Time Limit
- 30 min
- All Stages
- Required
EXCEPTIONS
- Network
- Resume
- Offline
- Wait
- Retry Limit
- Fail
FAILURE DETECTION & RECOVERY
Even when something fails,
keep the work that is already done.
Problems during a run, such as a dropped network, an offline device or full storage, are detected and recovered according to the policies you defined.
Devices and files that finished normally are kept, and only the part with a problem is processed again, which avoids unnecessary re-transfers.
RECOVERY
- Device CNetwork connection lost
- Offline
- Recovery
- Auto Resume
- Status
- Completed
CONTRACT VALIDATION
Every file can arrive
and the success conditions still not be met.
Whether the files were transferred and whether the Contract was met are judged separately.
See clearly why a condition was not met, such as a missing required target, an integrity mismatch or exceeding the allowed time.
VALIDATION
- File Transfer
- Success
- Integrity
- Verified
ASSURANCE ANALYSIS
See why errors happened
and how they were recovered.
Errors, recovery attempts and the final state of every run are recorded, so recurring problems stand out.
Analyze changes in device status and when errors occurred, and use them to improve transfer settings and run policies.
EVENT LOG
- Connection LostDevice C, 10:21
- Recovery AttemptRetry 1, 10:22
- Transfer ResumedCompleted, 10:23
FREQUENTLY ASKED QUESTIONS
Flow operations and Assurance,
frequently asked questions
Can I see the progress of a whole Multi-Stage Flow on one screen?
Studio Runs shows the overall Flow run status and the progress of each stage.
Can I see which device and file a transfer stopped at?
Select a stage and a device to see the per-file transfer history and where it stopped.
How is Assurance different from ordinary transfer monitoring?
Monitoring shows the progress and results of transfers, while Assurance is designed to verify the final result against success conditions and exception handling policies defined in advance.
Can Assurance fail even when the file transfer succeeded?
Yes. Even if every file arrived, the Contract can fail if the run went over the allowed time or did not meet a required business condition.
What conditions does an Assurance Contract define?
It defines the basic success conditions, such as required targets, file integrity, completion time and completion of the final stage, and the exception handling policies for situations such as network disconnection, devices going offline and running out of storage.
If only some devices fail, do the healthy devices have to transfer again?
Under the recovery policy you set, devices and files that completed normally are kept and only the targets with a problem are retried.
Can I see how many errors and recovery attempts there were?
Assurance is designed to record and analyze the errors, recovery attempts and final status of each run.
Can I find devices that fail repeatedly?
Device status history and the periods when errors occurred help you find recurring problems and improve your operating policies.
GET STARTED