{"id":"data-transfers.same-transfer-added-twice","url":"/faq/data-transfers/same-transfer-added-twice","category":{"id":"data-transfers","title":"Data Transfers"},"subcategory":{"id":"progress-and-control","title":"Progress, pausing and history"},"question":"Why didn't a new transfer appear when I added it a second time?","alt_questions":["duplicate transfer ignored","new transfer not added to list","start transfer did nothing","same sync twice","transfer already in progress"],"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.","answer_markdown":"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.\n\nWait 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.\n\nRelated: [How many transfers run at once?](/faq/data-transfers/how-many-transfers-run-at-once)","answer_html":"

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.

\n

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.

\n

Related: How many transfers run at once?

","answer_text":"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.\n\nWait 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.\n\nRelated: How many transfers run at once?","tags":["duplicates","queue"],"related":[{"id":"data-transfers.how-many-transfers-run-at-once","question":"How many transfers run at the same time?","url":"/faq/data-transfers/how-many-transfers-run-at-once"},{"id":"data-transfers.transfer-states-explained","question":"What do the transfer states like Queued, Running and Failed mean?","url":"/faq/data-transfers/transfer-states-explained"}],"applies_to":"all","last_reviewed":"2026-10-01","title":"Why didn't a new transfer appear when I added it a second time? — Storage Studio FAQ","description":"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.","crumbs":[{"name":"Home","path":"/"},{"name":"FAQ","path":"/faq/"},{"name":"Data Transfers","path":"/faq/data-transfers/"},{"name":"Why didn't a new transfer appear when I added it a second time?","path":"/faq/data-transfers/same-transfer-added-twice"}],"jsonld":{"@context":"https://schema.org","@type":"FAQPage","url":"https://storagestudio.us/faq/data-transfers/same-transfer-added-twice","inLanguage":"en","dateModified":"2026-10-01","mainEntity":[{"@type":"Question","name":"Why didn't a new transfer appear when I added it a second time?","alternateName":["duplicate transfer ignored","new transfer not added to list","start transfer did nothing","same sync twice","transfer already in progress"],"acceptedAnswer":{"@type":"Answer","text":"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.\n\nWait 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.\n\nRelated: How many transfers run at once?","url":"https://storagestudio.us/faq/data-transfers/same-transfer-added-twice"}}]},"fragment":"
\n
\n\n\n\n\n
\n
\n

Data Transfers · Progress, pausing and history

\n

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

\n

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.

\n

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.

\n

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.

\n

Related: How many transfers run at once?

\n\n

Last reviewed

\n\n

Related questions

\n

Also available as Markdown and JSON.

\n
"}