Page 1 of 1

New version leaving files behind??

PostPosted: Mon May 09, 2016 10:15 am
by kevinrmoon
I had a rule that would grab files, run an automator action and then move the files to a new location. Now after the 4.o upgrade, it is leaving a few random files untouched in the original folder. If I trigger the rule again, it will grab the remaining files, but I cannot figure out why it is missing them all of the sudden? I even built a 20 second pause into my automator action to wait for the files to come in, but it doesn't have any impact. Any help would be appreciated.

Re: New version leaving files behind??

PostPosted: Mon May 09, 2016 10:43 am
by Mr_Noodle
Check the logs and see if there were any errors moving those files. You can either post them here or email them in to support.

Re: New version leaving files behind??

PostPosted: Mon May 09, 2016 10:54 am
by kevinrmoon
Here is the log info, it left 3 random files untouched. I don't know what has changed from Version 3 to 4, but it was working perfectly before the upgrade. Thanks for any help you give me.


2016-05-09 10:51:29.836 hazelworker[5474] IMG_0164 copy.JPG: Rule Group Paste matched.
2016-05-09 10:51:31.975 hazelworker[5474] [File Event] File moved: IMG_0164 copy.JPG moved from folder /Users/Shared/Groups to Render/Test to folder /Volumes/12TBServer/Group Spooler.
2016-05-09 10:51:31.981 hazelworker[5474] IMG_0164.JPG: Rule Group Paste matched.
2016-05-09 10:51:34.195 hazelworker[5474] [File Event] File moved: IMG_0164.JPG moved from folder /Users/Shared/Groups to Render/Test to folder /Volumes/12TBServer/Group Spooler.
2016-05-09 10:51:34.198 hazelworker[5474] Cycle detected. Skipping file: IMG_0171 copy.JPG
2016-05-09 10:51:34.201 hazelworker[5474] IMG_0171.JPG: Rule Group Paste matched.
2016-05-09 10:51:36.232 hazelworker[5474] [File Event] File moved: IMG_0171.JPG moved from folder /Users/Shared/Groups to Render/Test to folder /Volumes/12TBServer/Group Spooler.
2016-05-09 10:51:36.239 hazelworker[5474] IMG_0173 copy.JPG: Rule Group Paste matched.
2016-05-09 10:51:36.297 hazelworker[5488] Groups to Render: Rule Thumbs.db matched.
2016-05-09 10:51:36.298 hazelworker[5488] File Test is busy. Skipping for now.
2016-05-09 10:51:38.295 hazelworker[5474] [File Event] File moved: IMG_0173 copy.JPG moved from folder /Users/Shared/Groups to Render/Test to folder /Volumes/12TBServer/Group Spooler.
2016-05-09 10:51:38.300 hazelworker[5474] IMG_0173.JPG: Rule Group Paste matched.
2016-05-09 10:51:40.445 hazelworker[5474] [File Event] File moved: IMG_0173.JPG moved from folder /Users/Shared/Groups to Render/Test to folder /Volumes/12TBServer/Group Spooler.
2016-05-09 10:51:42.463 hazelworker[5474] Test: Rule Subfolder Selection matched.
2016-05-09 10:51:44.313 hazelworker[5488] Groups to Render: Rule Thumbs.db matched.
2016-05-09 10:51:44.314 hazelworker[5488] File Test is busy. Skipping for now.
2016-05-09 10:51:44.476 hazelworker[5474] Test: Rule Subfolder Selection matched.
2016-05-09 10:51:44.480 hazelworker[5474] Done processing folder Groups to Render
2016-05-09 10:51:50.120 hazelworker[5488] Caught signal: 15

Re: New version leaving files behind??

PostPosted: Mon May 09, 2016 12:17 pm
by kevinrmoon
It seems like I see this line in the log file when it skips an image, but I don't know what it means.

"2016-05-09 12:14:42.702 hazelworker[6009] Cycle detected. Skipping file: IMG_0152.JPG"

Re: New version leaving files behind??

PostPosted: Mon May 09, 2016 8:39 pm
by kevinrmoon
Is there somewhere we can download Version 3? It was working fine in that, so I am contemplating dialing back a version if possible. ""UPDATE"" I uninstalled 4 and reinstalled 3.3.8 and rebuilt all my rules and everything is working fine again, obviously there is a flaw with 4 regarding the cycling of files.

Re: New version leaving files behind??

PostPosted: Tue May 10, 2016 9:22 am
by Mr_Noodle
I don't think this is something that changed between versions, at least from what the logs indicate.

The cycle thing means you are moving the file out of the folder but something keeps moving it back in. If that happens enough, then Hazel detects that as a cycle and will stop processing the file. It may happen as well if you keep adding files with the exact same name.

Also, I see a message in one case where a file is busy. Hazel won't process it until whatever program has that file open closes it.

Re: New version leaving files behind??

PostPosted: Wed Jun 01, 2016 10:49 am
by dredhorse
I can confirm this issue.

The rule is matched and running, but only to 50%... I have a lot of files with numbers... all odd numbers are processed the even are not process, if I force run the rules the rest will go to.

The logs indicate that the rules are processed but without manual running the rules nothing happens.

Is there anything specific I should look out for in the logs to explain such an issue?

Re: New version leaving files behind??

PostPosted: Wed Jun 01, 2016 3:03 pm
by Mr_Noodle
You'll have to post or email your logs. Also, go through the troubleshooting guide here: https://www.noodlesoft.com/kb/hazel-tro ... ing-guide/

Make sure the problem isn't because of files not matching what you think.

Re: New version leaving files behind??

PostPosted: Thu Jun 02, 2016 3:14 am
by dredhorse
I will probably create a support request for it.

Files are matching, like I said.... file 001.jpg is moved, file 002.jpg is not moved.

Go into hazel, run rules on folder, file 002.jpg is moved.

Re: New version leaving files behind??

PostPosted: Thu Jun 02, 2016 4:27 am
by roosterboy
Yep, I've been seeing this exact same issue as well since the upgrade. Thought I was going nuts. All of the files in a particular folder match my rule but only some of them actually have the rule executed on them. Worked perfectly under 3.whatever. And it happens with multiple folders, too, so it's clearly not something wrong with one particular rule.

I'll try to grab a log the next time I see it happen.

Re: New version leaving files behind??

PostPosted: Thu Jun 02, 2016 10:40 am
by Mr_Noodle
Don't assume it's the same problem. Almost every case I've found of this has been different. Make sure to email in your logs, your rules and details about what files were expected to be processed by which rules, and when that was supposed to happen but didn't.