{
  "schema": "https://storagestudio.us/schema/wiki-page.v1",
  "title": "Sync again and Run again",
  "slug": "sync-again",
  "url": "https://storagestudio.us/wiki/sync-again",
  "markdown_url": "https://storagestudio.us/wiki/sync-again.md",
  "category": "Data Transfers",
  "category_url": "https://storagestudio.us/wiki/data-transfers/",
  "tags": [
    "data transfers",
    "sync",
    "cloud accounts"
  ],
  "summary": "A finished, failed or cancelled transfer offers Sync again (for syncs) or Run again (for copies and moves), which repeats it with the same settings and sends only what changed since last time.",
  "published_at": "2026-10-01T06:19:26.000Z",
  "updated_at": "2026-10-01T05:33:49.000Z",
  "headings": [
    {
      "level": 2,
      "text": "Where to find it",
      "id": "where-to-find-it"
    },
    {
      "level": 2,
      "text": "What it sends",
      "id": "what-it-sends"
    },
    {
      "level": 2,
      "text": "Settings a repeat run doesn't carry over",
      "id": "settings-a-repeat-run-doesn-t-carry-over"
    },
    {
      "level": 2,
      "text": "When it isn't offered",
      "id": "when-it-isn-t-offered"
    },
    {
      "level": 2,
      "text": "Run again on a repeating transfer",
      "id": "run-again-on-a-repeating-transfer"
    }
  ],
  "links_out": [
    {
      "slug": "copy-move-sync-or-two-way-sync",
      "label": "Copy, Move, Sync or Two-way sync",
      "exists": true,
      "url": "https://storagestudio.us/wiki/copy-move-sync-or-two-way-sync"
    },
    {
      "slug": "dry-run",
      "label": "Trying a transfer first with Dry run",
      "exists": true,
      "url": "https://storagestudio.us/wiki/dry-run"
    },
    {
      "slug": "two-way-sync-first-run",
      "label": "Two-way sync and the First run box",
      "exists": true,
      "url": "https://storagestudio.us/wiki/two-way-sync-first-run"
    },
    {
      "slug": "transfer-schedules",
      "label": "Scheduling a transfer",
      "exists": true,
      "url": "https://storagestudio.us/wiki/transfer-schedules"
    },
    {
      "slug": "data-transfers",
      "label": "Data Transfers",
      "exists": true,
      "url": "https://storagestudio.us/wiki/data-transfers"
    },
    {
      "slug": "transfers-and-restarts",
      "label": "What happens to transfers when you restart",
      "exists": true,
      "url": "https://storagestudio.us/wiki/transfers-and-restarts"
    },
    {
      "slug": "a-transfer-failed",
      "label": "A transfer failed",
      "exists": true,
      "url": "https://storagestudio.us/wiki/a-transfer-failed"
    }
  ],
  "links_in": [
    {
      "slug": "a-transfer-failed",
      "title": "A transfer failed",
      "url": "https://storagestudio.us/wiki/a-transfer-failed"
    },
    {
      "slug": "copy-move-sync-or-two-way-sync",
      "title": "Copy, Move, Sync or Two-way sync",
      "url": "https://storagestudio.us/wiki/copy-move-sync-or-two-way-sync"
    },
    {
      "slug": "data-transfers",
      "title": "Data Transfers",
      "url": "https://storagestudio.us/wiki/data-transfers"
    },
    {
      "slug": "files-that-change-during-a-transfer",
      "title": "Files that change while they're being transferred",
      "url": "https://storagestudio.us/wiki/files-that-change-during-a-transfer"
    },
    {
      "slug": "ai-access",
      "title": "Letting another AI assistant read your storage",
      "url": "https://storagestudio.us/wiki/ai-access"
    },
    {
      "slug": "transfer-schedules",
      "title": "Scheduling a transfer",
      "url": "https://storagestudio.us/wiki/transfer-schedules"
    },
    {
      "slug": "dry-run",
      "title": "Trying a transfer first with Dry run",
      "url": "https://storagestudio.us/wiki/dry-run"
    },
    {
      "slug": "two-way-sync-first-run",
      "title": "Two-way sync and the First run box",
      "url": "https://storagestudio.us/wiki/two-way-sync-first-run"
    },
    {
      "slug": "transfers-and-restarts",
      "title": "What happens to transfers when you restart",
      "url": "https://storagestudio.us/wiki/transfers-and-restarts"
    }
  ],
  "diagrams": [
    {
      "kind": "flowchart",
      "caption": "What a repeat run does with each file",
      "outline": "- You click Sync again or Run again\n  - leads to Both sides are compared\n- Both sides are compared\n  - leads to Is the file the same on both sides?\n  - leads to Sync one-way only: extra files at the destination?\n- Is the file the same on both sides?\n  - Yes: leads to Skipped\n  - No, new or changed: leads to Transferred\n- Sync one-way only: extra files at the destination?\n  - Yes: leads to Deleted from the destination\n",
      "source": "%% caption: What a repeat run does with each file\nflowchart TD\n  A[You click Sync again or Run again] --> B[Both sides are compared]\n  B --> C{Is the file the same on both sides?}\n  C -->|Yes| S[Skipped]\n  C -->|No, new or changed| T[Transferred]\n  B --> D{Sync one-way only: extra files at the destination?}\n  D -->|Yes| X[Deleted from the destination]"
    }
  ],
  "images": [],
  "screenshots_pending": [
    {
      "alt": "The Data Transfers window with a completed Copy selected and the Run again button highlighted in the details pane",
      "caption": "Run again on a finished transfer"
    }
  ],
  "faqs": [],
  "text": "Sync again and Run again repeat a transfer you've already set up, with the same source, destination and settings. The transfer compares both sides and sends only what is new or has changed, so topping up a large folder is quick when little has changed. Where to find it Select a transfer in the Data Transfers list. Once it has Completed , Failed or been Canceled , the button row at the top of its details shows: Sync again for a Sync (one-way) or a Bidirectional sync ; Run again for a Copy or a Move . The new run appears in the same row of the list as the earlier ones, with the run count going up by one. What it sends Each run looks at both sides and transfers only the differences: new files, and files whose size, date or content has changed. Files that already match are left alone. That makes Sync again the easy way to bring a big folder up to date, or to finish a transfer that failed or was cancelled part-way — files that had finished aren't sent a second time. The operation still behaves as it always does. A Sync (one-way) run still deletes files at the destination that aren't in the source, and a Bidirectional sync run still carries deletions both ways. See Copy, Move, Sync or Two-way sync . What a repeat run does with each file Flowchart outline: What a repeat run does with each file You click Sync again or Run again leads to Both sides are compared Both sides are compared leads to Is the file the same on both sides? leads to Sync one-way only: extra files at the destination? Is the file the same on both sides? Yes: leads to Skipped No, new or changed: leads to Transferred Sync one-way only: extra files at the destination? Yes: leads to Deleted from the destination Settings a repeat run doesn't carry over Dry run is switched off. Running a dry run again performs the transfer for real — handy once you've checked the preview, but worth knowing. See Trying a transfer first with Dry run . First run for this pair is never carried over for a Bidirectional sync . That box is for the very first run only; see Two-way sync and the First run box . When it isn't offered While the transfer is still running, queued or paused. Use Pause , Resume or Cancel instead. For a Download. A large download already picks up where it left off when it's resumed. For a Move (Overwrite) started from Data Parking , because the source is gone once that kind of move finishes. If the same transfer is already running, clicking the button again doesn't start a second copy of it. Run again on a repeating transfer A repeat of a scheduled transfer runs in the background at low priority, like its scheduled runs. It doesn't change the schedule — the next scheduled run still happens at its usual time. See Scheduling a transfer . More answers are in the Storage Studio FAQ . See also: Data Transfers · What happens to transfers when you restart · A transfer failed",
  "markdown": "**Sync again** and **Run again** repeat a transfer you've already set up, with the same source, destination and settings. The transfer compares both sides and sends only what is new or has changed, so topping up a large folder is quick when little has changed.\n\n## Where to find it\n\nSelect a transfer in the **Data Transfers** list. Once it has **Completed**, **Failed** or been **Canceled**, the button row at the top of its details shows:\n\n- **Sync again** for a **Sync (one-way)** or a **Bidirectional sync**;\n- **Run again** for a **Copy** or a **Move**.\n\nThe new run appears in the same row of the list as the earlier ones, with the run count going up by one.\n\n## What it sends\n\nEach run looks at both sides and transfers only the differences: new files, and files whose size, date or content has changed. Files that already match are left alone. That makes **Sync again** the easy way to bring a big folder up to date, or to finish a transfer that failed or was cancelled part-way — files that had finished aren't sent a second time.\n\nThe operation still behaves as it always does. A **Sync (one-way)** run still deletes files at the destination that aren't in the source, and a **Bidirectional sync** run still carries deletions both ways. See [Copy, Move, Sync or Two-way sync](https://storagestudio.us/wiki/copy-move-sync-or-two-way-sync).\n\n```mermaid\n%% caption: What a repeat run does with each file\nflowchart TD\n  A[You click Sync again or Run again] --> B[Both sides are compared]\n  B --> C{Is the file the same on both sides?}\n  C -->|Yes| S[Skipped]\n  C -->|No, new or changed| T[Transferred]\n  B --> D{Sync one-way only: extra files at the destination?}\n  D -->|Yes| X[Deleted from the destination]\n```\n\n*Flowchart — What a repeat run does with each file. Outline:*\n\n- You click Sync again or Run again\n  - leads to Both sides are compared\n- Both sides are compared\n  - leads to Is the file the same on both sides?\n  - leads to Sync one-way only: extra files at the destination?\n- Is the file the same on both sides?\n  - Yes: leads to Skipped\n  - No, new or changed: leads to Transferred\n- Sync one-way only: extra files at the destination?\n  - Yes: leads to Deleted from the destination\n\n## Settings a repeat run doesn't carry over\n\n- **Dry run** is switched off. Running a dry run again performs the transfer for real — handy once you've checked the preview, but worth knowing. See [Trying a transfer first with Dry run](https://storagestudio.us/wiki/dry-run).\n- **First run for this pair** is never carried over for a **Bidirectional sync**. That box is for the very first run only; see [Two-way sync and the First run box](https://storagestudio.us/wiki/two-way-sync-first-run).\n\n## When it isn't offered\n\n- **While the transfer is still running, queued or paused.** Use **Pause**, **Resume** or **Cancel** instead.\n- **For a Download.** A large download already picks up where it left off when it's resumed.\n- **For a Move (Overwrite) started from Data Parking**, because the source is gone once that kind of move finishes.\n\nIf the same transfer is already running, clicking the button again doesn't start a second copy of it.\n\n## Run again on a repeating transfer\n\nA repeat of a scheduled transfer runs in the background at low priority, like its scheduled runs. It doesn't change the schedule — the next scheduled run still happens at its usual time. See [Scheduling a transfer](https://storagestudio.us/wiki/transfer-schedules).\n\nMore answers: https://storagestudio.us/faq\n\nSee also: [Data Transfers](https://storagestudio.us/wiki/data-transfers) · [What happens to transfers when you restart](https://storagestudio.us/wiki/transfers-and-restarts) · [A transfer failed](https://storagestudio.us/wiki/a-transfer-failed)\n"
}