What happened: the files behind a run

MFT 4 · 3:28

Two records show what a transfer's runs moved: the journal has one row per file, and each run publishes a run record with its counts. You can read both in the admin UI and in the terminal.

Download the mp4Recorded on 2026.2

What it covers

The Transferred files page, with its search and its filters for the last 30 days
The Transfers section on the transfer's own page
The same rclone lines in the terminal with weikio logs
The run record on the environment's event stream, with its counts of files, bytes and errors
The Runs section, one row per run, and the view a row opens
Listing runs with weikio events list and printing one with weikio events show

Commands in this video

Terminal

$ weikio logs finance/supplier-invoices --env devtest
$ weikio events list --env devtest --family mft --integration supplier-invoices
$ weikio events show --env devtest --stream events --seq 2

Transcript

0:02This video reads the two records the transfer's two runs left behind.
0:10The drawing shows your Weik.io installation as the earlier videos left it.
0:14In devtest agent dev runs the transfer at version 0.1.1 with a *.pdf filter.
0:22Two runs copied one PDF each to the bucket.
0:26price-list.csv didn't match, so it stayed on the supplier's server.
0:34The journal of moved files starts in the admin UI, on the Transferred files page.
0:40Every file a transfer moved has a row there,
0:42newest first, inside the window printed at the top.
0:46The bright row is invoice-1042.pdf,
0:50the newest on the page and the second run's file.
0:54price-list.csv has no row,
0:58because a file the filter holds back writes no line anywhere.
1:04The same journal is on the transfer's page, as its Transfers section.
1:14weikio logs for the transfer in devtest reads the same journal in the terminal.
1:19Weik.io keeps every line rclone writes during a run as rclone wrote it,
1:24so this command prints them back.
1:26The bright line is the second run's copy:
1:29the file name and its size stand in rclone's message.
1:35Each run also publishes a summary,
1:37which Weik.io keeps on the environment's event stream.
1:41The run record holds when the run started and when it finished.
1:44It also counts the files that moved,
1:47the bytes they carried and the errors the run met.
1:54Every run has a row in the Runs section on the transfer's page.
1:58A row carries when the run started, how long it took,
2:02how many files it moved, the size, the errors and the operation.
2:06A row opens that run's view, with its details,
2:10the two ends it worked between and the files it moved.
2:17weikio events list for devtest,
2:20the mft family and the supplier-invoices transfer prints a row per run.
2:25A row carries the number the record holds, the stream that keeps it,
2:30when it was stored, the family, the agent and the record's size.
2:34The newest row is the second run, kept on the stream the bright chip names.
2:42weikio events show prints the record at the number the listing printed,
2:47with the stream named as events.
2:49Its subject names the stream the record lies in,
2:52while its headers carry the transfer and the agent.
2:55Under the headers the body holds the project, the transfer,
2:59the start and end, and the counts the chip names.
3:05Every moved file left a row in the journal:
3:08the page, the section and the terminal's lines.
3:12Every run left a record on the stream, in the Runs section,
3:16the run's view and the two terminal commands.

Next in this track

MFT 5 · 4:27 To production