Runs and transferred files
Weik.io 2026.2Check which files a transfer moved, and find out why a run failed. Product page · Video
Watch: What happened: the files behind a run, 3:28
The video opens a run and lists the files it moved. Then it finds the log line of each file.
This part of the video couldn't be loaded.
On this page
rclone writes a log line for each file a transfer moves while the run is still going. The admin UI and the CLI show these lines and the summary that each run ends with.
A run and its files#
Open a run in the Runs section of the transfer’s page in the admin UI to see each file it moved and its size.




To check that a file arrived without knowing which transfer moved it, open Integrations › Transferred files, which lists the files of every transfer in one table.




The log line of each file#
$ weikio logs finance/supplier-invoices --env production --since 24hThe command prints each line as the JSON object rclone wrote. Weik.io logs every line at INFO, so look for rclone’s own level in the object’s level field.
| Field | What it has |
|---|---|
msg |
Copied or Moved for a moved file |
object |
The file |
size |
The file’s size |
The last line of a run is rclone’s stats, which totals the files and bytes the run transferred and counts its errors.
These lines are the transfer’s audit trail for each file, kept for as long as the installation keeps its logs, 30 days by default. The same permissions apply to them as to other log lines.
Each line has labels that say where it came from:
- The integration
- The version
- The project
- The environment
- The agent
The run summary#
Each run publishes one summary as an event in its environment, where other integrations can react to it. When the hub doesn’t store a summary, such as while the agent’s link to the hub is down, the summary is kept on the agent’s host. Once the agent reaches the hub again, it publishes the kept summaries oldest first. For each kept summary, the transfer’s logs have a warning that starts with The hub didn't store the summary of run.
A version of the transfer built before Weik.io 2026.2.3 instead tries to publish the summary again for about five minutes.
List the summaries with the CLI:
$ weikio events list --env production --family mft --integration finance/supplier-invoices --since 24h --with-bodyThe list has one row per run. --with-body adds each run’s summary:
- The run’s ID
- The start time
- The end time
- The number of files
- The number of bytes
- The number of errors
- The first error rclone wrote
The log lines of a run carry the run’s ID as their correlation ID. Show one run’s lines with it:
$ weikio logs finance/supplier-invoices --env production --since 24h --correlation-id 5f0c6d2e-8a41-4b7e-9c3d-2a1e7b9f4c60A failed run#
A run that ends with errors fails with its first error as the reason. Weik.io raises a problem that points to the run. The problem includes the weikio logs command that shows what rclone wrote in the run. Until a later run counts no errors, the problem shows in the admin UI and the CLI:
- Needs attention on Home
- The Observability Overview
- The transfer’s page
weikio problems




For a failure such as a missing folder or a refused password, the lines around the first error are in the logs under the run’s correlation ID.
When the installation keeps no logs#
An installation set up with --no-observability has no log store, so a run’s files and Transferred files show Transfer history isn't stored here. The Runs section still lists the run summaries. To keep the lines in your own log system, use Telemetry forwarding.