A transfer failed
When a transfer in Data Transfers shows Failed, select it to read what happened in plain English, fix what the message points to, then use Run again or Sync again — only what didn't arrive is sent.
When a transfer shows Failed in Data Transfers, select it: the details pane says in plain English what happened, lists up to five of the files that weren't copied, and keeps the last lines of its log. Sort out what the message points to, then click Run again (or Sync again). Only files that changed or didn't arrive are sent the second time.
What you might see
The details card starts with a short summary. The most common ones:
| Message begins | What to try |
|---|---|
| … couldn't be copied because they changed on the source while they were being copied | Let those files settle, for example by quitting the app writing them, then run it again. Everything else was copied. |
| … couldn't be copied because the account didn't allow reading or writing them (permission denied). | Check you can open those files in the account itself, and that the account isn't read-only. Test connection on the account confirms it still signs in. |
| … couldn't be copied because the destination ran out of space. | Free space at the destination, or choose a different one. |
| … couldn't be copied because they were no longer there when the copy reached them. | The files were moved or deleted during the transfer. Run it again if you still need them. |
| … couldn't be copied because the connection dropped while copying them. | Check your internet connection, then run it again. |
| The transfer didn't finish. | Read the Details: line and the Log card, then run it again. |
| The transfer stopped with error … | The last lines of the log follow. Run it again; if it fails the same way, contact support. |
| Transfer failed because the S3 bucket couldn't be found. | Edit the account, set the Bucket field to the right name, and run it again. |
Each summary also says how much was copied — "Copied … files (…) and checked … items." — and lists what wasn't under "Not copied:".
Two states aren't failures and sort themselves out:
- Waiting for drive — the transfer is waiting for a drive to come back. Use Check drive once it's plugged in.
- Needs space — the destination is full. Free some space and click Try again, or Move to another drive.
Files that were still being written when they were copied are handled for you: the transfer finishes as Completed and says it's fetching them again, or that "They'll be copied on the next run."
Flowchart outline: Recovering from a failed transfer
- Transfer shows Failed
- leads to Select it and read the summary
- Select it and read the summary
- leads to What does it point to?
- What does it point to?
- Files changing: leads to Let them settle
- Permission: leads to Check the account with Test connection
- Out of space: leads to Free space or pick another destination
- Connection: leads to Check your internet connection
- Let them settle
- leads to Click Run again or Sync again
- Check the account with Test connection
- leads to Click Run again or Sync again
- Free space or pick another destination
- leads to Click Run again or Sync again
- Check your internet connection
- leads to Click Run again or Sync again
- Click Run again or Sync again
- leads to Completed?
- Completed?
- No, same message: leads to Contact support with diagnostic logs
How to fix it
- Open Data Transfers… from the More menu and select the failed transfer.
- Read the summary and the Details: line. The Log card below shows the last lines of the transfer's log.
- Deal with what it names — space, the account's permissions, your connection, or files that were in use.
- Click Run again — Sync again for a sync. For most transfers it appears once a transfer has completed, failed or been cancelled. "Runs this transfer again with the same settings. Only files that changed since last time are sent."
- If an account needs signing in again, see When an account needs signing in again.
See also: Data Transfers · Sync again and Run again · Files that change while they're being transferred · What happens to transfers when you restart · Something's not working: start here
What links here
- Bandwidth limit and files at once
- Copying between two cloud accounts
- Data Transfers
- Files that change while they're being transferred
- Parking a folder in a cloud account
- Something's not working: start here
- Sync again and Run again
- Testing, editing and removing an account
- Trying a transfer first with Dry run
- What happens to transfers when you restart
- When an account needs signing in again