hi everyone,
I have an automator workflow running as a folder action script. The “enable folder actions” button is ticked. Occassionally, the script will not run because the folder actions have disabled themselves - has anyone else had this or know why it happens? I’m guessing network activity etc. might be the cause, but any tips would be very helpful!
cheers.
I haven’t run into this. Have you been able to determine the circumstances that cause the folder action to become disabled? Think about these:
Is it after a reboot? or a logout/back in?
What programs are running at the time? Is that folder open in the Finder?
Is Automator open when it disables, or not?
Look for those kinds of events and maybe test a bit.
I have a script which works well on two macs at work but no end of problems with two others.
All four should be the same build. But I suspect there is something slightly different on the two that it does not work on.
On the none working two, the Folder Actions either refuse to attach, Folder Actions get disabled, or Folder actions Show it is enabled when in fact its is not. Our IT basically refuse to support Folder Actions because they are so unreliable.
What I did find is at logon if I had a script to kill and re-activate “system events” the folder actions would act normally.
The script acts on network folders, I would say this is part of the problem along with “system events” but I do not get a problem with two of the macs?
Mark, I am having a similar problem. Could you post the script that worked for you?
Many Thanks,
Dave
It is simply telling “System Events” to quit and then activate
Save it as an app and add it to startup items
tell application "System Events" to quit
delay 5
tell application "System Events" to activate