{"id":"performance-battery.why-didnt-my-scheduled-tidy-up-run","url":"/faq/performance-battery/why-didnt-my-scheduled-tidy-up-run","category":{"id":"performance-battery","title":"Performance & battery"},"subcategory":{"id":"background-pauses","title":"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.","answer_markdown":"Usually because one of Storage Studio's courtesy rules held it back. Common reasons:\n\n- **Quiet Hours** — you were active, below your battery threshold, in a meeting, or inside a scheduled quiet window.\n- **Paused** — automatic actions are paused (the popover header is orange); click **Resume**.\n- **Asleep** — the Mac was asleep at the scheduled time.\n- **Heavy load** — Storage Studio had paused itself, or you're in Minimum mode.\n- **Drive disconnected** — moves to the fast drive need it plugged in.\n\nCheck the popover's **Last run** line and **Job Insights** for what happened. More in [the Troubleshooting manual](/manual/troubleshooting).","answer_html":"

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

\n\n

Check the popover's Last run line and Job Insights for what happened. More in the Troubleshooting manual.

","answer_text":"Usually because one of Storage Studio's courtesy rules held it back. Common reasons:\n\n- Quiet Hours — you were active, below your battery threshold, in a meeting, or inside a scheduled quiet window.\n- Paused — automatic actions are paused (the popover header is orange); click Resume.\n- Asleep — the Mac was asleep at the scheduled time.\n- Heavy load — Storage Studio had paused itself, or you're in Minimum mode.\n- Drive disconnected — moves to the fast drive need it plugged in.\n\nCheck the popover's Last run line and Job Insights for what happened. More in the Troubleshooting manual.","tags":["schedule","automatic actions","quiet hours"],"related":[{"id":"performance-battery.how-do-i-see-what-storage-studio-is-doing-in-the-background","question":"How can I see what Storage Studio is doing in the background right now?","url":"/faq/performance-battery/how-do-i-see-what-storage-studio-is-doing-in-the-background"},{"id":"settings.how-do-i-stop-everything-storage-studio-does-in-the-background","question":"How do I stop everything Storage Studio does in the background?","url":"/faq/settings/how-do-i-stop-everything-storage-studio-does-in-the-background"}],"applies_to":"all","last_reviewed":"2026-10-01","title":"Why didn't Storage Studio's scheduled tidy-up run when I expected? — Storage Studio FAQ","description":"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.","crumbs":[{"name":"Home","path":"/"},{"name":"FAQ","path":"/faq/"},{"name":"Performance & battery","path":"/faq/performance-battery/"},{"name":"Why didn't Storage Studio's scheduled tidy-up run when I expected?","path":"/faq/performance-battery/why-didnt-my-scheduled-tidy-up-run"}],"jsonld":{"@context":"https://schema.org","@type":"FAQPage","url":"https://storagestudio.us/faq/performance-battery/why-didnt-my-scheduled-tidy-up-run","inLanguage":"en","dateModified":"2026-10-01","mainEntity":[{"@type":"Question","name":"Why didn't Storage Studio's scheduled tidy-up run when I expected?","alternateName":["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"],"acceptedAnswer":{"@type":"Answer","text":"Usually because one of Storage Studio's courtesy rules held it back. Common reasons:\n\n- Quiet Hours — you were active, below your battery threshold, in a meeting, or inside a scheduled quiet window.\n- Paused — automatic actions are paused (the popover header is orange); click Resume.\n- Asleep — the Mac was asleep at the scheduled time.\n- Heavy load — Storage Studio had paused itself, or you're in Minimum mode.\n- Drive disconnected — moves to the fast drive need it plugged in.\n\nCheck the popover's Last run line and Job Insights for what happened. More in the Troubleshooting manual.","url":"https://storagestudio.us/faq/performance-battery/why-didnt-my-scheduled-tidy-up-run"}}]},"fragment":"
\n
\n\n\n\n\n
\n
\n

Performance & battery · Why background work waits or pauses

\n

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

\n

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.

\n

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

\n
  • 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.
\n

Check the popover's Last run line and Job Insights for what happened. More in the Troubleshooting manual.

\n\n

Last reviewed

\n\n

Related questions

\n

Also available as Markdown and JSON.

\n
"}