Currently Being ModeratedMar 10, 2013 5:37 AM (in response to Paul J. Lucas)
I found that a newer program I downloaded had added something to startup. Went to universal access and unclicked what it had clicked. restarted and all was well. No decoding necessary.
Currently Being ModeratedAug 16, 2013 4:26 AM (in response to Paul J. Lucas)
Hi Paul, I was having these messages for several years plus many other issues with previously working applescripts for folder actions since OSX 10.7 (now 10.8). I feel I have a great resolution for this that is DOCUMENTED by apple and now works 100% for all our production apple script folder actions.
You will see thes launchd messages dissappear mostly unless you have a very very active scripts.. as mentioned in the applestack post. I feel this is because the method of dispatch has changed to more reianle method than legacy method.. just a guess.
try this link I just posted. If your former applescript folder action was rock solid then became erratic and unpredictable in OSX 10.7 or 10.8, you simply need to attach an AUTOMATOR "folder ACTIONS" workflow node to the folder and change the "event handler" from the "add items on recipts etc etc" to "on run..."....
The Automator.app's "folder action" "run applescript" workflow node contains 99.% of your original applescript you use current.
You just need to change the handler.. so simple.
see this link I just posted .https://discussions.apple.com/thread/4237919?start=30&tstart=0
Post your results for others to see.