Noodlesoft Forums

A two-year old set of Hazel routines has failed to perform since last September. The routines, one each for each vendor, identified, re-tagged, retitled, and sent to Evernote statements downloaded from FileItFetch. Just noticed it.

I have about ten routines, one per vendor, and all use the same script except for customized tags. Here is the Applescript I use, borrowed from here:

tell application "Evernote"
activate
create note from file theFile notebook {"Statements"} tags {"TIAA", "Retirement"}
end tell

The tags are obviously changed for each vendor's routine. I suspect the scripts stopped working, but I don't know why. The originals are also absent because I recklessly sent them to Trash after "sending" them to Evernote (just changed this).

Questions:
Is there a better script out there? Did anything change in September to cause these scripts to derail (upgrades, etc)? Does a program such as Evernote have to be booted first before any successful activations? Is there a way to trap "didn't activate" errors in AS? Has anything in Hazel changed that would adversely affect performance of two-year-old routines? Finally, the Hazel logs seem to archive to a Prior Log monthly. Any way to extend the archive period going forward or retrieve older logs?

Sorry if these are basic. Its been two years since I last seriously dabbled with Hazel; the memory fades. As always, thanks in advance for your help. John

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

That should help isolate the problem.

There were two confounding problems. First, for reasons I don't know, Hazel ceased to recognize dates for one vendor. But I made use of the new (to me) auto date detect feature, and that solved one problem. The other nine date recognizing routines haven't failed, yet.

The other problem was exogenous to Hazel so I won't bore you.

For future reference, do I need to specify that I have read and followed the troubleshooting page tips? I may not deserve more, but I wanted more advice than "see troubleshoot". But perhaps you were wise to let me stew. JV

If you did already do the troubleshooting steps, then you should post the results as it is necessary to isolate the problem. Without that info, I can't really give much advice.