Hazel v6.0.4, running on an Apple Silicon Mac mini, macOS v15.5
I'm a longtime Hazel user, and am suddenly having an issue with a rule I haven't changed in years.
I have a rule for my "Downloads" folder that moves Newly Added files to a folder with the format of the current date (eg 2025-06-22). This has worked flawlessly, but in the last couple of weeks, Hazel tries to move the file while it is still downloading. When the file completes, it moves it again. This results with 2 files in the date-named folder: a zero byte file with the correct name (e.g., blah.dmg) and the actual full file named, e.g., blah-1.dmg.
As I said, I've changed nothing I'm aware of.
Any thoughts? Additional information needed?
EDITED TO ADD: It appears this may be the result of switching to Firefox a few weeks back. I think I have a workaround. It appears that when Firefox starts a download, it creates a zero byte file with the name of the file being downloaded. That file remains at zero bytes, but a file with the same name and a ".part" extension actually grows in size as the file downloads. When the download is done, the zero byte file is deleted and the .part file is renamed to the actual filename.
I added "extension is not part" and "size is greater than 0 bytes" to my trigger conditions, and now nothing happens until the full file is in the download folder with the correct name and size.
Is this just "a Firefox thing"?