---
id: moving-folders.why-was-my-move-blocked-for-recent-writes
url: https://storagestudio.us/faq/moving-folders/why-was-my-move-blocked-for-recent-writes
category: "Moving folders"
subcategory: "Folders an app is using"
question: "Why was my move blocked because of recent writes?"
alt_questions:
  - "Blocked folders with recent writes"
  - "What is the recent-write guard?"
  - "Storage Studio won't move a folder I just edited"
  - "Enable Bypass recent-write guard"
  - "move refused because files were modified recently"
short_answer: "A file in that folder changed recently (within 12 hours by default), so Data Parking holds it to avoid copying a folder that's still being written. Only busy folders are held. Wait, shorten the window, or bypass the guard in the gear settings."
tags: ["recent writes", "blocked", "data parking"]
related: ["https://storagestudio.us/faq/moving-folders/how-do-i-change-data-parking-settings", "https://storagestudio.us/faq/moving-folders/what-does-move-when-closed-mean"]
applies_to: "all"
last_reviewed: 2026-10-01
---

# Why was my move blocked because of recent writes?

Because a file in that folder was changed recently, which suggests something may still be writing to it. Moving a folder mid-write — a project during a build, a download still arriving — can leave a copy that's half one moment and half another, so Data Parking holds those folders and names the file that tripped the check.

By default "recently" means within the last 12 hours. Only the busy folders are held; the rest of your selection still moves.

Your options:

- Wait until the work has finished, then move it.
- Change the **Recent-write window** (1 to 72 hours) in Data Parking's gear.
- When you deliberately want to move work in progress, tick **Bypass recent-write guard** — only when you're sure nothing is writing.

See [Data Parking settings](https://storagestudio.us/faq/moving-folders/how-do-i-change-data-parking-settings)