Noodlesoft Forums

I am having some problems that seem inconsistent. I have Hazel monitor a folder for new downloads. When one matches the criteria it should Rename, Run Automator Workflow (which imports to a DTPO group), Move (to folder trash).

My problem is that it renames the file fine but does not run the workflow. I am using the workflow from this entry: viewtopic.php?f=4&t=3277#p12320

It used to work now it does not.

Thanks

Check the logs and make sure the workflow is running without error. Post whatever you find there.

Thanks for the suggestion.

Currently, I uninstalled everything and reinstalled. As I was at my wit's end. Everything seems to be working. I suspect, due to the files that were uninstalled, that there might have been some sort of conflict in the software through various upgrades. I really do not know as it has always been an inconsistent problem.

I will post more if I continue to have problems.

This is getting extremely troublesome and I need to deal with it. The original problem still exists.

I have a rule to process a folder and change file names in that folder. Then, pass the file to an Automator workflow that will pass the file to DTPO into a certain group. Then move the original file to the trash. It renames the file but never passes the file to the workflow. If i check the "quickly" for that folder it shows that the file matches the conditions but it does not do anything with it. The workflow works on its own.

I have checked the logs and there do not seem to be any errors.

The strange thing is that after a reboot it works as expected.

Can you describe the folder you have Hazel monitoring in this case? Is it a folder on your local drive? Is it a Dropbox folder?

It is a folder on my local drive. A couple deep in the Documents folder. Here are screen shots of my workflows:

Okay, I guess I do not know how to post an image here.

You can use an image hosting service like imgur.com.

When it happens again, make sure to check your logs. See if there's any activity when you add a file.

Still having the same problem. It used to intermittently work. It just does not want to run the Automator script. In the quicklook it shows the folder matched.

https://www.dropbox.com/s/m0lv79d8bwxrqs0/Screen%20Shot%204.png?dl=0
https://www.dropbox.com/s/rafh3jvxp1c6nno/Screen%20Shot%205.png?dl=0

Log file:
https://www.dropbox.com/s/1fgqiawzfqs4ue4/Logs.rtf?dl=0

Thanks for the help

It seems to run ok. The logs would indicate a problem running the Automator workflow. Not being a user of DevonThink, I don't know what the inputs of those Automator actions do. They would need to take in a file as input for anything to happen, I'd think.

It seems as if Hazel is not consistently passing the file to the Automator script. It happens sometimes, but not all the time and I cannot figure out why.

When Hazel renames a file, is that file then "selected" (or passed) to the workflow? The workflow is designed to act on the selected file (at least, that is my understanding, I am no expert).

I have edited the workflow to trigger a Finder "open" dialog box. It never does that. So I am thinking that the workflow is never triggered by Hazel to run.

Thanks for the help.

When using Automator with Hazel, do not use anything related to the selected file. That relies on Finder's current state which is a dangerous way to do things. Hazel will pass in the file; you just have to make sure the first action in the workflow takes files as input.

Okay. How you suggest is how I have it set up.

A new piece I have discovered and not sure if you can help in this.

While looking at Activity Monitor, it seems the stall, or pickup, is in a process called "Automator Runner". Several of those run, it seems one per hazel process that calls such. They eventually turn red (Not Processing). There is also a process called Script Monitor that turns red and (Not Processing). When I quit this process, the rest of the Hazel processes (rule steps) after the workflow run.

I managed to grab these files from Activity Monitor on the Automator Runner process but forgot to get one on Script Monitor. Will try that later. Thanks again.

https://www.dropbox.com/s/oeacfaveavlyn ... r.txt?dl=0
https://www.dropbox.com/s/mo77qgflqgqq2 ... 6.png?dl=0

I've seen issues with that before which indicated to me that Automator is a bit glitchy at times. Have you tried a simpler Automator workflow that doesn't involve DevonThink? See if that works as it may help isolate the problem.