Rules involving "Date last opened" don't work

Hello, I'm trying to get Hazel to mark newly added unopened files to be labeled Green, and opened files to be removed of a label. I used the sample rule in Hazel to mark new files green which worked but when I create a rule to mark them opened it never works everything stays green. Also one weird thing is file downloaded from firefox have the date last opened matched to the date created and modified. Even though the date last opened is after the date created/modified it still doesn't work. I checked the files info and it correctly displays the last date opened but for some reason Hazel isn't correctly reading them.

Do you have this problem for multiple file types? I experienced something similar for PDFs, but not for dmgs, docs, or zip files.

Could you email me your rules? If you are registered, you can use the export function, otherwise, screenshots would work. If you have a sample file which consistently shows this, then zip it up and send that as well (make sure to zip it as it should hopefully preserve the dates). Click the "Contact Support" link in the "Info" tab for the email address.

Also, I'm assuming you are looking at the "Last Opened" in Finder and not going off the access date in Terminal.

Thanks.

Will do! I already have a .zip file that I've unzipped and unzipped but it still shows up as new and not opened. Thanks for the help I hope this can be resolved.

I've the same problem...
Some times it works, and sometime not. Does it make any difference how I open the file?

My rule: http://grab.by/112d

Thanks for your help
Michael

The way to check is to do "Get Info" on the file in Finder and look at the "Last opened" value under "More Info". I don't recall which ways of opening a file will update that value so you need to experiment.

You can also check against the date modified to make sure your rule should be firing (it may be that the last opened date is not what you thought). I'd also suggest using the rule preview to see if files are matching properly there. If things are ok there then finally check the logs.