DISTRIBUTION RESULTS & ASSURANCE
Distributed to 100 devices?
Then check all 100 results.
Tell completed, failed and incomplete devices apart in the overall result, and check file status per device.
If some devices did not receive their files, or the job did not finish on time, Assurance judges the result against your business success conditions.
- Per-device resultsCompleted, incomplete and failed devices
- Per-file statusWhich files reached each device
- Assurance verdictFinal verdict against business conditions
Factory A software distribution
Central Linux Server → Factory A, 100 devicesStudio / Runs
- Completed
- 96
- Incomplete
- 3
- Failed
- 1
| Target device | Files | Result |
|---|---|---|
| factory-a-001 | 3 / 3 | Completed |
| factory-a-043 | 2 / 3 | Incomplete |
| factory-a-044 | 1 / 3 | Incomplete |
| factory-a-045 | 0 / 3 | Failed |
DEVICE & FILE RESULTS
Distribution results, by device and by file.
Select a device in the overall result to see which files were delivered to it and which are still incomplete.
Search by filename to find the status of a specific file, and if the transfer was interrupted, see exactly how far it got.
Central Linux → factory-a-043
RunsFactory Afactory-a-043
| File | Size | Result |
|---|---|---|
application.bin | 2.4 GB | Completed |
config.json | 12 KB | Completed |
release-notes.txt | 24 KB | Incomplete |
- Target path
/opt/application/
EXCEPTION HANDLING & RECOVERY
A failure never repeats a completed delivery.
Wait, retry or skip policies apply to exceptions such as network drops, insufficient storage and offline devices.
Devices that completed normally are left alone; recovery targets only the devices and files that had a problem.
Recovery attempts and the final result are recorded in the run history.
Recovery status, Factory A
| Device | Issue | Recovery |
|---|---|---|
| factory-a-043 | Network interrupted | Recovered |
| factory-a-044 | Insufficient storage | Recovered |
| factory-a-045 | Device offline | Recovered |
factory-a-043, application.bin
100%Resumed from the interruption point, completed files kept- Completed devices
- 96, unchanged
Only the 3 affected devices were recovered, and all 100 are now complete. The recovery attempts are in the run history.
DISTRIBUTION ASSURANCE CONTRACT
All 100 delivered, but late? That may not be success.
An Assurance Contract defines the success conditions, such as required devices, required files, destination, file integrity and completion deadline.
Even when the file transfer is technically complete, an unmet contract condition is judged a business failure.
Factory A software distribution
04:00, Distribution started06:20
EXECUTION HISTORY & ASSURANCE ANALYSIS
Every result is recorded, so recurring problems stand out.
For each run, see the error count, recovery attempts, final state and Contract verdict.
When a device keeps dropping its network or running out of storage, analyze its run history and device status together.
Use the findings to improve device checks, run schedules and exception policies for the next distribution.
Factory A distribution
Execution history
| Run | Errors | Recoveries | Contract |
|---|---|---|---|
| Nov 09 | 4 | 3 | Failed |
| Nov 08 | 2 | 2 | Passed |
| Nov 07 | 3 | 3 | Passed |
| Nov 06 | 1 | 1 | Passed |
Repeated issue3 occurrences
- factory-a-043
- Network interruptions
- Last 3 runs
- Nov 07, Nov 08, Nov 09
Review connection history and recovery attempts before the next distribution.
FAQ
Distribution results & Assurance
Can I see the distribution results for all devices at once?
Yes. Runs shows the overall result and the completed, incomplete and failed status of each device.
Can I check which files reached a specific device?
Yes. The per-device file details let you search by filename and see the result of each file.
If a distribution is interrupted, can I see how far it got?
Yes. Completed and incomplete files are listed separately along with their transfer status.
Can I redistribute only to the devices that failed?
Yes. Depending on the recovery policy, completed devices are kept and only failed or incomplete devices are retried.
What happens when a device is offline or out of storage?
The configured exception policy applies, such as wait, retry or skip.
What is an Assurance Contract?
A set of business success conditions, such as required devices, required files, destination, integrity and completion deadline, against which the distribution result is evaluated.
Can Assurance fail even when every device completed?
Yes. Even with every file delivered, the Contract can fail if the deadline was exceeded or another required condition was not met.
Can I see the errors and recovery attempts during a distribution?
Yes. Errors, recovery attempts and the final result are recorded and traceable per run.
Can I find devices that keep having problems?
Yes. Run history and device status records help analyze recurring failures and the causes of distribution delays.
Can the Assurance success conditions be changed?
Yes. A default Contract is provided, and success conditions and exception policies can be adjusted to your operational requirements.
GET STARTED