{"id":"data-transfers.why-was-a-scheduled-run-skipped","url":"/faq/data-transfers/why-was-a-scheduled-run-skipped","category":{"id":"data-transfers","title":"Data Transfers"},"subcategory":{"id":"scheduling","title":"Scheduling transfers"},"question":"Why didn't a scheduled transfer start at its usual time?","alt_questions":["scheduled run skipped","scheduled transfer late","why is my sync not running on schedule","schedule didn't fire","scheduled transfer delayed"],"short_answer":"A run is held back if the previous one for the same pair is still active, if your Mac is under heavy load (it starts later), if the app wasn't running, or if the external drive isn't connected.","answer_markdown":"A few things hold a scheduled run back on purpose:\n\n- **The previous run is still going** (or waiting for the drive, or paused) for the same source and destination. The new run is skipped rather than piling up behind it.\n- **Your Mac is under heavy load.** Storage Studio holds back background work so your own work comes first; the run starts a little later, once things settle. Nothing is skipped.\n- **Storage Studio wasn't running or the Mac was asleep.** It catches up once when it's back.\n- **The drive isn't connected.** The run waits in *Waiting for drive*.\n\nRelated: [Do schedules run when the app is closed?](/faq/data-transfers/do-schedules-run-when-the-app-is-closed) · [“Waiting for drive”](/faq/data-transfers/what-does-waiting-for-drive-mean)","answer_html":"

A few things hold a scheduled run back on purpose:

\n\n

Related: Do schedules run when the app is closed? · “Waiting for drive”

","answer_text":"A few things hold a scheduled run back on purpose:\n\n- The previous run is still going (or waiting for the drive, or paused) for the same source and destination. The new run is skipped rather than piling up behind it.\n- Your Mac is under heavy load. Storage Studio holds back background work so your own work comes first; the run starts a little later, once things settle. Nothing is skipped.\n- Storage Studio wasn't running or the Mac was asleep. It catches up once when it's back.\n- The drive isn't connected. The run waits in Waiting for drive.\n\nRelated: Do schedules run when the app is closed? · “Waiting for drive”","tags":["schedule","delayed","skipped"],"related":[{"id":"data-transfers.do-schedules-run-when-the-app-is-closed","question":"Do scheduled transfers run if Storage Studio is closed or my Mac is asleep?","url":"/faq/data-transfers/do-schedules-run-when-the-app-is-closed"},{"id":"data-transfers.what-does-waiting-for-drive-mean","question":"What does “Waiting for drive” mean on a transfer?","url":"/faq/data-transfers/what-does-waiting-for-drive-mean"},{"id":"data-transfers.schedule-a-recurring-transfer","question":"How do I schedule a transfer to run automatically?","url":"/faq/data-transfers/schedule-a-recurring-transfer"}],"applies_to":"all","last_reviewed":"2026-10-01","title":"Why didn't a scheduled transfer start at its usual time? — Storage Studio FAQ","description":"A run is held back if the previous one for the same pair is still active, if your Mac is under heavy load (it starts later), if the app wasn't running, or if the external drive isn't connected.","crumbs":[{"name":"Home","path":"/"},{"name":"FAQ","path":"/faq/"},{"name":"Data Transfers","path":"/faq/data-transfers/"},{"name":"Why didn't a scheduled transfer start at its usual time?","path":"/faq/data-transfers/why-was-a-scheduled-run-skipped"}],"jsonld":{"@context":"https://schema.org","@type":"FAQPage","url":"https://storagestudio.us/faq/data-transfers/why-was-a-scheduled-run-skipped","inLanguage":"en","dateModified":"2026-10-01","mainEntity":[{"@type":"Question","name":"Why didn't a scheduled transfer start at its usual time?","alternateName":["scheduled run skipped","scheduled transfer late","why is my sync not running on schedule","schedule didn't fire","scheduled transfer delayed"],"acceptedAnswer":{"@type":"Answer","text":"A few things hold a scheduled run back on purpose:\n\n- The previous run is still going (or waiting for the drive, or paused) for the same source and destination. The new run is skipped rather than piling up behind it.\n- Your Mac is under heavy load. Storage Studio holds back background work so your own work comes first; the run starts a little later, once things settle. Nothing is skipped.\n- Storage Studio wasn't running or the Mac was asleep. It catches up once when it's back.\n- The drive isn't connected. The run waits in Waiting for drive.\n\nRelated: Do schedules run when the app is closed? · “Waiting for drive”","url":"https://storagestudio.us/faq/data-transfers/why-was-a-scheduled-run-skipped"}}]},"fragment":"
\n
\n\n\n\n\n
\n
\n

Data Transfers · Scheduling transfers

\n

Why didn't a scheduled transfer start at its usual time?

\n

Short answer: A run is held back if the previous one for the same pair is still active, if your Mac is under heavy load (it starts later), if the app wasn't running, or if the external drive isn't connected.

\n

A few things hold a scheduled run back on purpose:

\n
  • The previous run is still going (or waiting for the drive, or paused) for the same source and destination. The new run is skipped rather than piling up behind it.
  • Your Mac is under heavy load. Storage Studio holds back background work so your own work comes first; the run starts a little later, once things settle. Nothing is skipped.
  • Storage Studio wasn't running or the Mac was asleep. It catches up once when it's back.
  • The drive isn't connected. The run waits in Waiting for drive.
\n

Related: Do schedules run when the app is closed? · “Waiting for drive”

\n\n

Last reviewed

\n\n

Related questions

\n

Also available as Markdown and JSON.

\n
"}