The morning after
You switched on automatic filing last night. This morning the invoice you need is gone from ~/Downloads, and you have no idea which folder took it.
Nothing is broken yet. Automatic filing works by moving files, and a move you did not see looks exactly like a disappearance.
So before you undo anything, find out where the thing went.
Find it first
Apple's support page "If you can't find a file on Mac" lists three ways that cover most cases. Open Spotlight, type part of the filename, and double-click the result; the file opens from wherever it now lives. Click Recents in the Finder sidebar, which groups items by Date Last Opened. Or check Apple menu > Recent Items.
One caveat about Recents belongs in the rumor column, not the fact column. Forum posts claim Recents depends on a "Last Used Date" attribute that only updates when you open a file through Finder, which would mean a file your automation touched never appears there. I could not find that in any Apple document, so I am not going to tell you it is true. Check Recents anyway, and if the file is not listed, do not read that as evidence of anything.
Spotlight is the one to trust. It searches by name, not by what you happened to open.
Undoing the move
Finder has an undo. Press Cmd+Z, or use Edit > Undo, and if a move was the last thing that happened the menu item reads "Move of x items." People have been pointing at this on Apple's community forums since at least November 2019, and MacMost's walkthrough states that "The Finder allows you to use Undo on deletions, moves and renames," with repeated undos often working several steps back. How many steps, nobody specifies.
Now the part I could not establish, which matters more than any of the above.
I found no documentation, from Apple or anyone else, on whether Finder's undo covers a move performed by a different application. I also found nothing on what happens to the undo history when Finder restarts. The common assumption, that Finder's undo only tracks Finder's own actions, sounds sensible and is written down nowhere I could find.
That leaves one practical rule: do not plan around Cmd+Z. Try it; it costs one keystroke. But any filing tool you rely on needs its own undo, because that undo is the one whose behavior is specified.
Hazel, the long-running Mac filing app, has one. Right-click a file and choose Revert, or use the menu bar icon. The manual lists which actions roll back: Move, Rename, Sort into subfolder, Add tags, Remove tags, Set color label, Add comment, Toggle extension, Toggle lock, Archive, Unarchive. It also lists what does not: Copy, Sync, Upload, Make alias, Import into Music, Photos or TV, and anything that ran an automation. Hazel's own manual calls the feature limited, and its release notes add that Revert "only reverts attributes on the file and will not undo effects on other apps/locations."
Read that second list before you build a rule that uploads things.
When undo is gone: Time Machine
Apple documents that "Time Machine saves one snapshot of your startup disk approximately every hour, and keeps it for 24 hours." No external drive required, provided your startup disk is APFS and "Back Up Automatically" is switched on. The snapshots survive "up to 24 hours or until space is needed on the disk."
To restore, open the window the item used to be in, open Time Machine from Spotlight, use the arrows beside the Finder window to move between backups, select the item, and click Restore. Apple's instructions say the item returns to its original location, exactly what you want after a bad move.
The 24-hour figure is the catch. A file your automation misfiled last Thursday is not in a local snapshot.
There is also an exception. A March 2024 writeup at eclecticlight.co states that files iCloud has evicted from local storage "can't be backed up by Time Machine while they're evicted (as their data isn't stored locally any more), and they can't be searched by Spotlight." A file that exists only in the cloud leaves no local copy to capture, and Spotlight will not surface it either. Two of your three recovery routes, closed at once.
The four things that actually break
Half-finished downloads
The oldest and most common one. August 2016, Hazel's forum, a user downloading with Safari into a Dropbox folder: "Hazel sees the incomplete download and moves it out of the way (incomplete) and Safari then complains that the file can't be written." The developer's answer: Hazel only recognizes Safari downloads inside the folder Safari is configured to use, so a download aimed anywhere else looks like an ordinary idle file. The fix was a rule pinned to the top of the list: Extension is download, Ignore file.
The same failure in a different costume, March 2015, mid-extraction: "Hazel is seeing this, and moving the file before the unrar is done, which obviously results in an incomplete file."
Anything written slowly is exposed. Big downloads, archive extraction, video exports.
Files that live in the cloud
In August 2022 Hazel's developer put it bluntly: "I would recommend against having it sync against iCloud. The files need to be local for Hazel to work properly and it's a bit of a toss-up with iCloud whether that is the case."
That warning later became a specific bug. After September 2025, on macOS Tahoe, Hazel 6.0.4 failed to move iCloud Drive files with Error Domain=NSPOSIXErrorDomain Code=11 "Resource deadlock avoided". The files were not local. Opening one in Preview first, which forces iCloud to pull the data down, let the move succeed.
According to the same eclecticlight.co writeup, when "Optimize Mac Storage" is on, iCloud can empty the local copy of a file and fetch it back only when something opens it. Point automation at a folder in that state and your rules reach for files that are not there.
Rules pointing at a disk that is gone
March 2025, after a Sequoia 15.3.1 upgrade: "none of my rules work with the Download folder." The cause: an old rule aimed at /Volumes/Data/Downloads, on an external drive no longer attached.
Nothing failed loudly. Nothing happened at all, the worse outcome, because you go on assuming your files are being filed.
Folder Actions quietly stopping
March 2022, macOS Monterey 12.3, Apple's community forums, with a long tail of "Me Too" replies: Folder Actions simply stop firing. The workaround people settled on: an AppleScript that toggles folder actions off and back on through System Events, wrapped as an Automator app and dropped into Login Items. Apple has no support document acknowledging any of this.
Which is the honest summary of built-in automation. When it stops, you hear about it from strangers.
Setting it up so it breaks less
Keep the folder your browser downloads into separate from the folder your automation watches, or at least exclude in-progress extensions in a rule that runs first. Do not watch a folder inside iCloud Drive while "Optimize Mac Storage" is on. Recheck every rule path after a macOS upgrade and after you retire an external drive, because a dead path produces silence rather than an error. And if you use Folder Actions, plan for the day it stops on its own.
On macOS Tahoe, Shortcuts gained folder automations that fire when items are Added, Modified, or Removed, handing the full list of changes to your shortcut. Six Colors called Apple's implementation "pretty basic," and the reason is in how it works: "the job of parsing, filtering, and acting on that information is entirely in the hands of the shortcut itself." A November 2025 update added an "Ignore subfolders" checkbox. The filtering is yours to write. All of it.
Ornix, and what it will not do for you
My app, Ornix, is in this category, so the uncomfortable half goes first.
Its undo works one file at a time. There is no undo-all. The history holds at most 50 moves and only 7 days of them, so a move from two weeks ago is out of reach. It has no search and no filter either, just a list and a button that wipes it.
It does not read your files. No OCR, no AI sorting; classification runs off extensions and UTType, nothing else. It does not detect duplicates by content, only name collisions. It has no condition-and-action rule builder, so if you want your own logic, buy Hazel: $42 for a single user, $65 for the Family Pack, $20 to upgrade, macOS 13 Ventura or later.
Its guard against half-written files is thin, and the section above explains why that matters. It skips four extensions, .tmp, .crdownload, .part and .download, plus hidden files. The logic that waited for a file's size to stop changing was removed; what remains is an existence check and a short pause, 0.1 seconds by default. A file written slowly under some other extension can still get grabbed mid-write.
What it does have is the undo I argued you should insist on, free rather than a Pro feature. When a file moves, the notification carries an Undo Move button. Later, open the History tab in settings, hover a card, and click the revert icon. The history survives quitting the app.
Undo refuses in two situations: the moved file is no longer where it was put, or a file with the same name already occupies the original location; it stops instead of overwriting. If the original folder itself was deleted, it recreates it. For 5 minutes after an undo it leaves that file alone, though it forgets that promise on restart.
Moves are real moves, not copy-then-delete. Seven default categories: Image, Video, Audio, Document, Compressed, Installer, Other, with Installer switched off by default on new folders. On a name collision you choose keep both with a number appended, replace, or skip, plus four follow-up options: replace and open the file, replace and open the folder, open the existing file, open the existing folder. The free tier watches one folder; Pro watches unlimited folders and resolves collisions automatically, $4.99 once, not a subscription. Scheduled cleanups are free. It needs macOS 14.0.
Filing software earns its keep in exactly one moment, and it is not the moment it tidies your desktop. It is the thirty seconds after it moves the wrong file.
