What this solves#
A rollout has finished and you have to report on it. Before writing "done", you need to know:
- How many of the 1,200 devices actually received it
- Which ones did not
- For a collection, which devices have still not sent
- Whether the file count matched but one file arrived corrupted
The answers are already on screen. They sit in three places, and few people know which place answers which question. This document covers those three.
Who this is for#
| Role | When |
|---|---|
| Operations | Reporting on an overnight rollout or collection |
| System administrator | Checking whether one device keeps dropping out |
| Quality and audit | Evidencing which file reached which device |
The three places#
| Place | What it answers fastest |
|---|---|
| Flow details | How many of how many this Flow finished on its last run |
| Runs | The full list of running and finished work, and one run's per-device and per-file results |
| Assurance | Whether the job succeeded, and how many were late or skipped |
If you are in a hurry, one line on Flow details is enough.
The fastest answer: Last run on the Flow details#
Open a Flow under Flows. Last run sits at the lower right.
Last run
Completed Today, 11:13
Duration 19s
Devices 3 of 3 completedDevices 3 of 3 completed is the "how many of how many" line. For a distribution it counts devices that received; for a collection, devices that sent.
Above it, the status tally:
Planned 0 Transferring 0 Completed 3 Failed 0Below that stands one table, headed by Transfer status and the device count beside it (1 device, or 3 devices). They are not tabs - there is nothing to press and there is only one table. It lists one row per device.
| Column | What it shows |
|---|---|
Device |
Device name |
Status |
Completed, Transferring, Recovering, Failed |
Progress |
Percentage |
Last activity |
When it last moved |
Normally there are four columns. Only while at least one device is actually transferring does Speed slot in between Progress and Last activity, making five. Once everything is finished or still planned the column disappears entirely - it does not sit there full of dashes. Four columns is not a broken screen.
Each row expands into that device's detail.
On the left, what this Flow sends:
What this flow sends
Source 3 devices
Source path 2 paths
Destination Seoul Render
Target path 3 paths
Filter All files
Save option Not setFinding things in the full list: Runs#
Runs has two tabs.
Activity tab — one row per transfer#
A distribution appears as one row per target device. Send to 1,200 devices and there are 1,200 rows. In exchange, you can filter straight down to a device.
There are eight columns, in this order: Transfer, Status, Progress, Flow, Files, Size, Started, Assurance.
The Transfer cell carries both ends of the route. The type is not a column - it rides in the row as a badge.
Five type badges tell you what kind of transfer it is at a glance:
| Badge | Meaning |
|---|---|
Direct |
One device to one device |
Distribution |
One to many |
Collection |
Many to one |
Many to many |
Several sources and several targets |
Chain |
Steps linked together |
Many to manyis rare on screen. It appears only when there are two or more sources and two or more targets, so you meet it only on transfers that are neither a distribution nor a collection. Not having seen it does not mean it is not there.
Four filters at the top narrow the list: All types, All flows, All statuses, All time.
Beside them sits a sort toggle - press Newest and it becomes Oldest (those are the two). To the left of the filters the current count reads like 11 transfers. Filtering lowers that number too, so it is where you read how many rows a filter left.
Flows tab — one row per Flow#
The same distribution collapses into one row. There are eight columns here too, in a different order - Flow, Status, Progress, Devices, Files, Size, Last run, Assurance. Activity's Transfer becomes Flow, and Started becomes Last run.
Do not trust the type badge on this tab. The same Flow showed
Chainon the Activity tab andDirecthere - a Flow that passes through three sites, whose row on this tab names only its two ends and drops the hop in the middle. The badge is decided by counting the stages in the transfer's list of legs, and this tab's row does not carry them, so it resolves as if there were one stage. Read the Activity tab, or the Flow's steps, to tell whether stages are linked.
The type badge rides beside the name in the Flow column, and the target count comes after the badge - Release Distribution Distribution 4. Direct carries no count (it has one target). A count means several targets; no count means one.
This tab has three filters - All types, All statuses, All time. All flows drops out (one row is one Flow, so there is nothing to filter). Showing 1-6 of 6 sits below.
The Devices column names only one representative pair (Singapore CDN → LA Studio PC). The rest appear when you open the row. Seeing one pair does not mean there is only one target.
The view switches at the top. There are three - List, Kanban, Map. The buttons carry icons, not words - the group is labelled View and each button names itself on hover. Kanban gives each status a column and each Flow a card; Map helps when sites are far apart.
Opening one run#
Press a row and a panel opens on the right.
- Status tally —
Planned 0 · Transferring 0 · Completed 4 · Failed 0 - Topology — the source node to the target group. Press the count badge on the group to draw every device, and
Group devicesto collapse them again - A heading, not tabs. Open one transfer and
Transferred filesheads the file table. Open a Flow that bundles several andTransfersstands there with a count beside it. There is nothing to press, and one table at a time. - Two ways to narrow the files —
Search filesby name, and the selector beside it by result (All files,Completed,Failed,Skipped) - The file table — one row per file per device
Its columns:
| Column | What it shows |
|---|---|
File |
File name |
Path |
Path |
Device |
Which device it went to |
Size |
Size |
Result |
Completed, Failed |
Time |
Time |
One file sent to four devices is four rows. "Which file on which device, and what happened" ends here. This is the screen to use for audit evidence.
Search files above the table narrows by name. The header's Search runs, flows, devices finds runs, Flows and devices from anywhere.
Reading it as a business result: Assurance#
A finished transfer and a successful job are different things. The Assurance screen and its report record the difference.
The Devices block in the report splits devices by state:
Devices 100 devices On time 100Devices 100 devices Late (latest +12m) 29 On time 71Devices 50 devices Skipped (left out of the rate) 1 Completed 49The grouping changes with the contract. With a deadline set, devices are grouped as
LateandOn time, as in the first two. Without one, they are grouped asCompleted,Completed with issuesandNot started, as in the third.Skippedappears either way, and the product itself annotates itleft out of the rate.
Watch the third one. A skipped device leaves the rate calculation. There were 50 targets, yet Target completion reads 49 / 49 targets with 1 skipped beside it and passes. Always quote the Skipped count in an operations report. See Decide in Advance What Happens When a Transfer Goes Wrong.
Two more lines sit below:
Issues & Recovery 1 recorded event · 3 recovery attempts · on 1 device
1 unresolved
Activity 8 events · 1 policy decisionThe second line of Issues & Recovery is the outcome: 1 unresolved while something was not recovered, Recovered automatically once everything was, and the whole line reads No issues when nothing happened.
Both lines open. Opening Issues & Recovery lists the issues, each with a state: Detected, Recovering, Waiting, Resolved or Unresolved. An issue left at Unresolved was not recovered. Do not leave it.
Checking a collection for gaps#
Distributions and collections read in opposite directions.
| Distribution | Collection | |
|---|---|---|
Devices N of M completed |
Devices that received | Devices that sent |
| Rows in the device table | Receiving devices | Sending devices |
Device in the file table |
Where it arrived | Where it came from |
The report changes its words too, not just their meaning. On a collection:
| Distribution | Collection |
|---|---|
Devices 100 devices … |
Source devices 12 devices … |
Target completion 100 / 100 targets |
Target completion 12 / 12 sources |
So a collection that lost two cameras reads 10 / 12 sources, and the block below it is Source devices 12 devices Failed 2 Completed 10.
In a collection, "has not sent yet" is any row in the device table that is not Completed. The Failed count in the tally and the Devices block in Assurance show the same thing two ways.
Missing files are known after the run, not before. The product cannot know what a device will produce today. What is absent at the destination is answered by Resend missing files, which re-reads the destination. See Four ways to send again.
Where to look, by situation#
| Situation | Where |
|---|---|
| One line for the morning report | Flow details, Last run, Devices N of M completed |
| The list of stores that missed out | The Transfer status table on the Flow detail → rows whose Status is not Completed |
| What went to one device | Run detail → file table → filter by Device |
| Which files failed | Run detail → file table → Result is Failed |
| Devices that missed the deadline | Assurance report → Devices → Late |
| Devices skipped by policy | Assurance report → Devices → Skipped |
| Only one Flow | Runs → All flows filter |
| Only failures | Runs → All statuses filter |
What a clean finish looks like#
- The status tally reads
Failed 0 Last runreadsDevices N of N completedContract Statusin Assurance isSatisfiedIssues & Recoveryin the report readsNo issues
With all four, the report can go out.
Errors and exceptions#
| What you see | Meaning | What to do |
|---|---|---|
Assurance column reads - |
Not judged yet, or no Assurance answer arrived | If a finished run stays -, check the server connection |
Partial completed |
Only some devices finished | Find which in the Transfer status table on the Flow detail. The Assurance report writes the same state as Partially completed |
Recovering |
Interrupted and recovering | Wait. It resumes by itself |
| The header count differs from the tab count | The header count can include the source device | Use the tab count |
| The file table is empty | Per-file results have not arrived yet | Look again once the run ends |
Stored at destination reads 8 / 10 with 2 not reported |
Two devices never sent their per-file results, so storage cannot be confirmed | The transfer itself succeeded. The contract goes Indeterminate, not Violated. Check those two devices' agents |
Operating notes#
- Do not report from
Completedalone. Read the skipped devices and anyUnresolvedalongside it. - The
Devicescolumn on the Flows tab is one representative pair, not the full target list. - One distribution is as many Activity rows as it has targets. With 1,200 devices the Flows tab is far easier.
- Map view helps only when sites are far apart. Devices in one building overlap.
- The file table is the evidence. Which file reached which device and when, one row each. This is the screen to show an auditor.
By industry#
| Industry | How it is used |
|---|---|
| Retail | One Last run line for the national picture in the morning, then pull the missed stores from the Transfer status table |
| Manufacturing | Per-line device table to check when each machine applied it, reading Last activity against the shift change |
| Finance | Keep the file table as evidence: which file reached which branch, row by row |
| Healthcare | Confirm collection per inspection device in the device table, then fill gaps with Resend missing files |
| Public sector | The Activity line and its N policy decisions count in the Assurance report document why things were handled as they were |
| Broadcast | Map view for site-to-site delivery, with late sites under Late |
See also#
- Four Ways to Send Again, and When to Use Each
- Define Transfer Success with an Assurance Contract
- Decide in Advance What Happens When a Transfer Goes Wrong — why a skipped device leaves the denominator