---
id: data-transfers.why-was-a-scheduled-run-skipped
url: https://storagestudio.us/faq/data-transfers/why-was-a-scheduled-run-skipped
category: "Data Transfers"
subcategory: "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."
tags: ["schedule", "delayed", "skipped"]
related: ["https://storagestudio.us/faq/data-transfers/do-schedules-run-when-the-app-is-closed", "https://storagestudio.us/faq/data-transfers/what-does-waiting-for-drive-mean", "https://storagestudio.us/faq/data-transfers/schedule-a-recurring-transfer"]
applies_to: "all"
last_reviewed: 2026-10-01
---

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

A few things hold a scheduled run back on purpose:

- **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*.

Related: [Do schedules run when the app is closed?](https://storagestudio.us/faq/data-transfers/do-schedules-run-when-the-app-is-closed) · [“Waiting for drive”](https://storagestudio.us/faq/data-transfers/what-does-waiting-for-drive-mean)