Data Transfers · Progress, pausing and history

Why didn't a new transfer appear when I added it a second time?

Short answer: A new transfer is ignored when one with the same source, destination and operation is already active. Let the existing one finish (or cancel it) and start again if you need another run.

Storage Studio ignores a new transfer if one with the same source, destination and operation is already active — queued, running, paused, waiting for the drive or waiting for space. The existing one already covers it, so a second copy would only repeat the work.

Wait for the existing transfer to finish (or cancel it) and start again if you need another run. A Copy and a Move between the same two places count as different transfers, so both can exist.

Related: How many transfers run at once?

Last reviewed

Also available as Markdown and JSON.