{
  "schema": "https://storagestudio.us/schema/wiki-page.v1",
  "title": "Two-way sync and the First run box",
  "slug": "two-way-sync-first-run",
  "url": "https://storagestudio.us/wiki/two-way-sync-first-run",
  "markdown_url": "https://storagestudio.us/wiki/two-way-sync-first-run.md",
  "category": "Data Transfers",
  "category_url": "https://storagestudio.us/wiki/data-transfers/",
  "tags": [
    "data transfers",
    "two-way sync",
    "sync"
  ],
  "summary": "A two-way sync (Bidirectional sync) needs the First run for this pair box ticked on its very first run, to set the starting point. Never tick it again for the same two folders — Storage Studio never carries it into later runs for you.",
  "published_at": "2026-10-01T06:20:03.000Z",
  "updated_at": "2026-10-01T05:33:52.000Z",
  "headings": [
    {
      "level": 2,
      "text": "Why there's a first run",
      "id": "why-there-s-a-first-run"
    },
    {
      "level": 2,
      "text": "Setting up a two-way sync",
      "id": "setting-up-a-two-way-sync"
    },
    {
      "level": 2,
      "text": "What happens if it's ticked again",
      "id": "what-happens-if-it-s-ticked-again"
    },
    {
      "level": 2,
      "text": "When the same file changes on both sides",
      "id": "when-the-same-file-changes-on-both-sides"
    },
    {
      "level": 2,
      "text": "Starting again with a new pair",
      "id": "starting-again-with-a-new-pair"
    }
  ],
  "links_out": [
    {
      "slug": "dry-run",
      "label": "Trying a transfer first with Dry run",
      "exists": true,
      "url": "https://storagestudio.us/wiki/dry-run"
    },
    {
      "slug": "restoring-from-a-backup",
      "label": "Restoring from a backup",
      "exists": true,
      "url": "https://storagestudio.us/wiki/restoring-from-a-backup"
    },
    {
      "slug": "transfer-schedules",
      "label": "Scheduling a transfer",
      "exists": true,
      "url": "https://storagestudio.us/wiki/transfer-schedules"
    },
    {
      "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": "glossary-two-way-sync",
      "label": "Two-way sync",
      "exists": true,
      "url": "https://storagestudio.us/wiki/glossary-two-way-sync"
    },
    {
      "slug": "sync-again",
      "label": "Sync again and Run again",
      "exists": true,
      "url": "https://storagestudio.us/wiki/sync-again"
    },
    {
      "slug": "files-that-change-during-a-transfer",
      "label": "Files that change during a transfer",
      "exists": true,
      "url": "https://storagestudio.us/wiki/files-that-change-during-a-transfer"
    }
  ],
  "links_in": [
    {
      "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": "copying-between-two-cloud-accounts",
      "title": "Copying between two cloud accounts",
      "url": "https://storagestudio.us/wiki/copying-between-two-cloud-accounts"
    },
    {
      "slug": "transfer-schedules",
      "title": "Scheduling a transfer",
      "url": "https://storagestudio.us/wiki/transfer-schedules"
    },
    {
      "slug": "sync-again",
      "title": "Sync again and Run again",
      "url": "https://storagestudio.us/wiki/sync-again"
    },
    {
      "slug": "dry-run",
      "title": "Trying a transfer first with Dry run",
      "url": "https://storagestudio.us/wiki/dry-run"
    },
    {
      "slug": "glossary-two-way-sync",
      "title": "Two-way sync",
      "url": "https://storagestudio.us/wiki/glossary-two-way-sync"
    }
  ],
  "diagrams": [
    {
      "kind": "flowchart",
      "caption": "When to tick the First run box",
      "outline": "- Setting up a Bidirectional sync\n  - leads to Has this exact pair of folders ever completed a two-way sync?\n- Has this exact pair of folders ever completed a two-way sync?\n  - No, this is the first time: leads to Tick First run for this pair\n  - Yes: leads to Leave it unticked\n- Tick First run for this pair\n  - leads to Later runs: Sync again or the schedule\n- Leave it unticked\n  - leads to Later runs: Sync again or the schedule\n- Later runs: Sync again or the schedule\n  - leads to These never use the First run box\n",
      "source": "%% caption: When to tick the First run box\nflowchart TD\n  A[Setting up a Bidirectional sync] --> B{Has this exact pair of folders ever completed a two-way sync?}\n  B -->|No, this is the first time| C[Tick First run for this pair]\n  B -->|Yes| D[Leave it unticked]\n  C --> E[Later runs: Sync again or the schedule]\n  D --> E\n  E --> F[These never use the First run box]"
    }
  ],
  "images": [],
  "screenshots_pending": [
    {
      "alt": "The New Transfer sheet with Bidirectional sync selected and Advanced options expanded, showing the First run for this pair checkbox and its orange warning text",
      "caption": "The First run box for a two-way sync"
    }
  ],
  "faqs": [],
  "text": "A two-way sync — Bidirectional sync in Data Transfers — needs one extra step the first time: tick First run for this pair in Advanced options . That first run sets the starting point Storage Studio compares against from then on. After it, the box must never be ticked again for the same two folders. Why there's a first run A two-way sync carries changes in both directions, including deletions. To know what changed — and on which side — it compares each folder with how both looked at the end of the previous run. On the very first run there is no previous run, so the first run builds that starting point by bringing the two folders together. Every later run works from it. Setting up a two-way sync Check the two folders. Ideally one of them is empty, or both already hold the same files. If both have different files in them, the first run brings them together, so make sure that's what you want. In Data Transfers , click New Transfer and choose Bidirectional sync . Fill in Source and Destination . For a two-way sync it doesn't matter much which is which, but keep them the same way round if you ever set it up again. Open Advanced options and tick First run for this pair . The box appears only for Bidirectional sync . Optionally tick Dry run (preview only) to rehearse it first — see Trying a transfer first with Dry run . If you do, set the transfer up again afterwards with the box ticked and Dry run off for the real first run. Choose a Schedule if you want it to repeat, then click Start Transfer . From then on, use Sync again or the schedule. Both always run without the first-run box, even when the original transfer had it ticked, so you can't tick it again by accident. When to tick the First run box Flowchart outline: When to tick the First run box Setting up a Bidirectional sync leads to Has this exact pair of folders ever completed a two-way sync? Has this exact pair of folders ever completed a two-way sync? No, this is the first time: leads to Tick First run for this pair Yes: leads to Leave it unticked Tick First run for this pair leads to Later runs: Sync again or the schedule Leave it unticked leads to Later runs: Sync again or the schedule Later runs: Sync again or the schedule leads to These never use the First run box What happens if it's ticked again Ticking the box on a later run throws away the starting point and builds a new one. The app warns that this would silently overwrite one side with the other — a change or deletion you made on one side since the last run could be undone by the other side. That's why the warning under the box is shown in orange, and why repeat runs never carry it. If you've already ticked it again by mistake, look through both folders for anything that came back or changed, and restore what you need from a backup — see Restoring from a backup . When the same file changes on both sides If one file was edited on both sides between two runs, Storage Studio can't know which edit you want. It records the clash as a conflict in the transfer's Log . To avoid conflicts: Let a sync finish before you edit the same file in the other place. Schedule runs often enough that the two sides don't drift far apart — see Scheduling a transfer . Avoid opening the same document on both sides at the same time. Starting again with a new pair The first-run step belongs to a pair of folders. If you change either folder — a different destination, or a renamed source — that's a new pair, and its first run needs the box ticked again. More answers are in the Storage Studio FAQ . See also: Copy, Move, Sync or Two-way sync · Two-way sync · Sync again and Run again · Files that change during a transfer",
  "markdown": "A two-way sync — **Bidirectional sync** in Data Transfers — needs one extra step the first time: tick **First run for this pair** in **Advanced options**. That first run sets the starting point Storage Studio compares against from then on. After it, the box must never be ticked again for the same two folders.\n\n## Why there's a first run\n\nA two-way sync carries changes in both directions, including deletions. To know what changed — and on which side — it compares each folder with how both looked at the end of the previous run. On the very first run there is no previous run, so the first run builds that starting point by bringing the two folders together. Every later run works from it.\n\n## Setting up a two-way sync\n\n1. Check the two folders. Ideally one of them is empty, or both already hold the same files. If both have different files in them, the first run brings them together, so make sure that's what you want.\n2. In **Data Transfers**, click **New Transfer** and choose **Bidirectional sync**.\n3. Fill in **Source** and **Destination**. For a two-way sync it doesn't matter much which is which, but keep them the same way round if you ever set it up again.\n4. Open **Advanced options** and tick **First run for this pair**. The box appears only for **Bidirectional sync**.\n5. Optionally tick **Dry run (preview only)** to rehearse it first — see [Trying a transfer first with Dry run](https://storagestudio.us/wiki/dry-run). If you do, set the transfer up again afterwards with the box ticked and **Dry run** off for the real first run.\n6. Choose a **Schedule** if you want it to repeat, then click **Start Transfer**.\n\nFrom then on, use **Sync again** or the schedule. Both always run **without** the first-run box, even when the original transfer had it ticked, so you can't tick it again by accident.\n\n```mermaid\n%% caption: When to tick the First run box\nflowchart TD\n  A[Setting up a Bidirectional sync] --> B{Has this exact pair of folders ever completed a two-way sync?}\n  B -->|No, this is the first time| C[Tick First run for this pair]\n  B -->|Yes| D[Leave it unticked]\n  C --> E[Later runs: Sync again or the schedule]\n  D --> E\n  E --> F[These never use the First run box]\n```\n\n*Flowchart — When to tick the First run box. Outline:*\n\n- Setting up a Bidirectional sync\n  - leads to Has this exact pair of folders ever completed a two-way sync?\n- Has this exact pair of folders ever completed a two-way sync?\n  - No, this is the first time: leads to Tick First run for this pair\n  - Yes: leads to Leave it unticked\n- Tick First run for this pair\n  - leads to Later runs: Sync again or the schedule\n- Leave it unticked\n  - leads to Later runs: Sync again or the schedule\n- Later runs: Sync again or the schedule\n  - leads to These never use the First run box\n\n## What happens if it's ticked again\n\nTicking the box on a later run throws away the starting point and builds a new one. The app warns that this would silently overwrite one side with the other — a change or deletion you made on one side since the last run could be undone by the other side. That's why the warning under the box is shown in orange, and why repeat runs never carry it.\n\nIf you've already ticked it again by mistake, look through both folders for anything that came back or changed, and restore what you need from a backup — see [Restoring from a backup](https://storagestudio.us/wiki/restoring-from-a-backup).\n\n## When the same file changes on both sides\n\nIf one file was edited on both sides between two runs, Storage Studio can't know which edit you want. It records the clash as a conflict in the transfer's **Log**. To avoid conflicts:\n\n- Let a sync finish before you edit the same file in the other place.\n- Schedule runs often enough that the two sides don't drift far apart — see [Scheduling a transfer](https://storagestudio.us/wiki/transfer-schedules).\n- Avoid opening the same document on both sides at the same time.\n\n## Starting again with a new pair\n\nThe first-run step belongs to a **pair** of folders. If you change either folder — a different destination, or a renamed source — that's a new pair, and its first run needs the box ticked again.\n\nMore answers: https://storagestudio.us/faq\n\nSee also: [Copy, Move, Sync or Two-way sync](https://storagestudio.us/wiki/copy-move-sync-or-two-way-sync) · [Two-way sync](https://storagestudio.us/wiki/glossary-two-way-sync) · [Sync again and Run again](https://storagestudio.us/wiki/sync-again) · [Files that change during a transfer](https://storagestudio.us/wiki/files-that-change-during-a-transfer)\n"
}