A transfer run failed
Weik.io 2026.2The newest run of a file transfer counted errors and some files weren't copied or moved, and the first error rclone wrote usually gives the cause. Video
Watch: To production, 4:27
The video promotes the transfer to production, where its two ends point at different systems.
This part of the video couldn't be loaded.
| Kind | Severity | Who sees it |
|---|---|---|
transfer- |
Error | Everyone who can read the transfer |
Its row in the problem list has a figure such as 1 error.
What it means#
The last run of a file transfer ended with errors, so some files weren’t copied or moved. The admin UI shows the transfer as Last run failed.
What raises it#
Weik.io checks the summary of each transfer’s newest run every 15 seconds, and a run that counted any error raises the problem. The detail gives the run’s start and end, its errors and files, the first error rclone wrote and the command that shows that run’s log. The problem clears when a later run counts no errors, and a stopped transfer raises none.
What to check#
Read what rclone wrote in the failed run, with the times and run id from the detail:
$ weikio logs <project>/<transfer> --env <environment> --from <start> --to <end> --correlation-id <run>List the transfer’s recent runs:
$ weikio events list --env <environment> --family mft --integration <project>/<transfer> --since 24hHow to fix it#
The first error usually says what went wrong: a password that changed, a host that can’t be reached, a full disk at the destination or a path that doesn’t exist. Fix the remote’s values, which come from the transfer’s variables and secrets, and the next scheduled run tries again. When a password changed, set the new one and restart the transfer so it uses it:
$ weikio secret set <project>/<secret> --env <environment> --restart