---
id: performance-battery.why-didnt-my-scheduled-tidy-up-run
url: https://storagestudio.us/faq/performance-battery/why-didnt-my-scheduled-tidy-up-run
category: "Performance & battery"
subcategory: "Why background work waits or pauses"
question: "Why didn't Storage Studio's scheduled tidy-up run when I expected?"
alt_questions:
  - "Automatic tidy-up didn't run last night"
  - "Last run time didn't change"
  - "storage studio daily run didn't happen"
  - "Why didn't the automatic move run overnight?"
  - "Automatic actions not running"
short_answer: "Usually a courtesy rule held it back: Quiet Hours, automatic actions paused, the Mac asleep, heavy load or Minimum mode, or the fast drive disconnected. Check Last run in the popover and Job Insights."
tags: ["schedule", "automatic actions", "quiet hours"]
related: ["https://storagestudio.us/faq/performance-battery/how-do-i-see-what-storage-studio-is-doing-in-the-background", "https://storagestudio.us/faq/settings/how-do-i-stop-everything-storage-studio-does-in-the-background"]
applies_to: "all"
last_reviewed: 2026-10-01
---

# Why didn't Storage Studio's scheduled tidy-up run when I expected?

Usually because one of Storage Studio's courtesy rules held it back. Common reasons:

- **Quiet Hours** — you were active, below your battery threshold, in a meeting, or inside a scheduled quiet window.
- **Paused** — automatic actions are paused (the popover header is orange); click **Resume**.
- **Asleep** — the Mac was asleep at the scheduled time.
- **Heavy load** — Storage Studio had paused itself, or you're in Minimum mode.
- **Drive disconnected** — moves to the fast drive need it plugged in.

Check the popover's **Last run** line and **Job Insights** for what happened. More in [the Troubleshooting manual](https://storagestudio.us/manual/troubleshooting).