Hazel consistently misses the last file put in a folder

Having a trouble with a chain of Hazel actions. For some reason, Hazel consistently misses when I add a file to a folder, unless I "wake" it up.

Here's the chain:

I get a file from Transmission. It downloads a file, and moves it a DOWNLOADED folder. Hazel sees the new file, makes an alias file, and moves the new alias file to a new folder called ALIAS.

That ALIAS folder is also monitored by Hazel. When it sees the new alias file added to the folder, it's supposed to run a terminal script that renames it. Once it's renamed, it moves that file to a few and final folder.

The problem is that when Hazel moves the file to the ALIAS folder, the file just sits there. If Transmission downloads a new file, the the FIRST file in the ALIAS folder will get moved, but now the second sits there. It's weird, it's like it always forgets to the last check.

The only thing I can think is that since Hazel is performing a series of events, maybe two are happening simultaneously and its missing one? But then Hazel is so good with multiple files... I don't know, I can't figure it out.

Any thoughts on why this might be happening?

I suggest going through the troubleshooting guide here: https://www.noodlesoft.com/kb/hazel-tro ... ing-guide/

That should help isolate where the problem is. Report back with the outputs from that.

Okay finally got around to looking in to this. According to the logs, its just not seeing that folder updating.

So right now, I download a file, and Hazel creates a symlink (using a bash script) from the file in /DOWNLOADED and saves to /ALIAS. So now /ALIAS has the symlinked file. But then the newly created file just sits in /ALIAS and Hazel doesn't trigger. I checked the logs and saw this:

Code: Select all: 2016-11-05 22:18:48.733 hazelworker[2349] Done processing folder DOWNLOADS - TORRENTS 2016-11-05 22:20:48.968 hazelworker[2588] ###main load address: 0x10fc66000 2016-11-05 22:20:48.969 hazelworker[2588] ###Noodle load address: 0x10fd7e000 2016-11-05 22:20:48.969 hazelworker[2588] ###CK load address: 0x10fd44000 2016-11-05 22:20:49.069 hazelworker[2588] Processing folder DOWNLOADS - TORRENTS 2016-11-05 22:20:51.149 hazelworker[2588] Done processing folder DOWNLOADS - TORRENTS

Nothing happened before that section for a while.

Now, if I go in and copy a new file into or delete a file from /ALIAS, it wakes up Hazel and it runs the script on the /ALIAS folder like its supposed to. It's just not seeing the most recent change for some reason. Here's the .log after the /ALIAS Hazel rule is run when I move a file into the /ALIAS folder manually.

Code: Select all: 2016-11-05 22:18:48.733 hazelworker[2349] Done processing folder DOWNLOADS - TORRENTS 2016-11-05 22:20:48.968 hazelworker[2588] ###main load address: 0x10fc66000 2016-11-05 22:20:48.969 hazelworker[2588] ###Noodle load address: 0x10fd7e000 2016-11-05 22:20:48.969 hazelworker[2588] ###CK load address: 0x10fd44000 2016-11-05 22:20:49.069 hazelworker[2588] Processing folder DOWNLOADS - TORRENTS 2016-11-05 22:20:51.149 hazelworker[2588] Done processing folder DOWNLOADS - TORRENTS 2016-11-05 22:25:54.266 hazelworker[2965] ###main load address: 0x10c7ec000 2016-11-05 22:25:54.267 hazelworker[2965] ###Noodle load address: 0x10c90b000 2016-11-05 22:25:54.267 hazelworker[2965] ###CK load address: 0x10c8d0000 2016-11-05 22:25:54.302 hazelworker[2965] Processing folder ALIAS 2016-11-05 22:25:56.330 hazelworker[2965] file1.mp4: Rule Rename and Move file matched. 2016-11-05 22:25:57.546 hazelworker[2965] file2.mp4: Rule Rename and Move file matched. 2016-11-05 22:25:57.785 hazelworker[2965] file3.mp4: Rule Rename and Move file matched. 2016-11-05 22:25:58.096 hazelworker[2965] file4.mp4: Rule Rename and Move file matched.

I'd also like to note that since I last posted this, I've bought a new computer, installed everything on that, moved my Hazel rules over and I'm still experiencing an identical issue. I have recently updated to Sierra, so maybe it has something to do with that? Although I think this was happening on El Capitan too.

Any thoughts?

Okay, I just tried moving stuff manually into the folder to see what happens just to get more specifics on this.

For whatever reason, Hazel doesn't seem to run the rule if files are added to /ALIAS. But if I delete a file from /ALIAS, that wakes Hazel up and it performs the rule.

Here's what happened this time:

Code: Select all: 016-11-05 22:46:21.950 hazelworker[5000] ###main load address: 0x10b6ef000 2016-11-05 22:46:21.951 hazelworker[5000] ###Noodle load address: 0x10b807000 2016-11-05 22:46:21.951 hazelworker[5000] ###CK load address: 0x10b7cd000 2016-11-05 22:46:21.981 hazelworker[5000] Processing folder ALIAS 2016-11-05 22:46:23.991 hazelworker[5000] file7.mp4: Rule Rename and Move file matched. 2016-11-05 22:46:24.740 hazelworker[5000] file8.mp4: Rule Rename and Move file matched. 2016-11-05 22:46:25.739 HazelHelper[373] Got event for path /Volumes/EXTERNAL 01/Download/DOWNLOADS/file7.mp4 that does not exist under monitored path /Volumes/EXTERNAL 01/MT 2016-11-05 22:46:25.739 HazelHelper[373] Got event for path /Volumes/EXTERNAL 01/Download/DOWNLOADS /file8.mp4 that does not exist under monitored path /Volumes/EXTERNAL 01/MT 2016-11-05 22:46:25.758 hazelworker[5019] ###main load address: 0x10379f000 2016-11-05 22:46:25.759 hazelworker[5019] ###Noodle load address: 0x1038be000 2016-11-05 22:46:25.759 hazelworker[5019] ###CK load address: 0x103883000 2016-11-05 22:46:25.797 hazelworker[5019] Processing folder DOWNLOADS 2016-11-05 22:46:26.763 hazelworker[5022] ###main load address: 0x101ed0000 2016-11-05 22:46:26.763 hazelworker[5022] ###Noodle load address: 0x101ff0000 2016-11-05 22:46:26.763 hazelworker[5022] ###CK load address: 0x101fb2000 2016-11-05 22:46:26.812 hazelworker[5022] Processing folder MT 2016-11-05 22:46:26.951 hazelworker[5000] File .DS_Store is busy. Skipping for now. 2016-11-05 22:46:27.887 hazelworker[5019] Done processing folder DOWNLOADS 2016-11-05 22:46:28.899 hazelworker[5022] Done processing folder MT 2016-11-05 22:46:28.975 hazelworker[5000] Done processing folder ALIAS

Are there any symlinks/aliases in the path? It seems like it is confusing things. Also, can you post your rule?

Yeah part of the script is creating a symlink.

Looks like you're right. It seems like Hazel doesn't see when symlinks are create or moved into the folder its watching. But if I delete a symlink from that folder, it does work.

As a workaround, I have an additional command running that just does "touch /Volume/Drive/ALIAS/temp.tmp"

That has been a good workaround for now.