A transfer run failed
Weik.io 2026.2The newest run of a file transfer ended with errors. You find the cause in the first error rclone wrote. Video
Watch: To production, 4:27
The video promotes the transfer to production. In production, 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 and didn’t copy or move some files. The admin UI shows the transfer as Last run failed.
What raises it#
When the summary of a transfer’s newest run counts any error, the problem shows within 15 seconds. It clears when a later run counts no errors. You don’t see it for a stopped transfer.
The problem’s detail shows the start and end of the failed run and its errors and files. It also shows the first error rclone wrote.
The detail also has the command that shows the run’s log.
What to check#
Read what rclone wrote in the failed run. Take the times and the run ID from the problem’s 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 shows what went wrong, for example:
- A password that changed
- A host that can’t be reached
- A full disk at the destination
- A path that doesn’t exist
Fix the remote’s values in the transfer’s variables and secrets. The next scheduled run then tries again. When a password changed, set the new one and restart the transfer:
$ weikio secret set <project>/<secret> --env <environment> --restart