Folder Action does not run on SECOND file only

The folder action will trigger when the first file hits the attached folder, so if the downloads are not complete you will need to add some kind of check or delay. Hard to tell without seeing the script - a folder action will also fail silently if there is an untrapped error.

Chris i have the same problem, i've implemented a script and i 've attached about 1000 folders, and than when i copy more than one file to one of theses folders, or some files are copied or it is never trigged, sometimes it simply does not work!!

I did a test, i run this applescript [tell application "System Events" to activate"] before copy the files, but it kept unstable, sometimes it works, sometime it does not work!

i did notfound anything aboutthis subjecton the Internet.

Please i need some help to solve this problem

Folder actions can be spotty, particularly when doing tasks that involve the Finder. I think what happens is that triggering a folder action script will make the dispatcher miss any files added while the script is running (and for a throttle period after), so adding files faster than about once every ten seconds can cause problems. Of course, the dispatcher is supposed to check periodically for missed files, but the default time for that is fairly long (3 minutes), and I'm not entirely convinced it works as advertised.

There are workarounds and alternate approaches, but we'd need to see the script in question.

Need more details:

• Are you using the Finder, System Events.app, or unix to change the file names?
• If you move in two or more files in the same drag, do they all get processed or just the first one?
• Do you get any errors in Console.app when the Folder action runs?
• If the script fails to fix a file, and you leave it alone for 15 minutes, is the file fixed in the interim?

In my case, i use both solutions

1- Automator running rsync (unix) to copy files, and i use the Finder to copy the new files to my external HD

2- When i use Finder, sametimes the event dispatch my actionscript, and move all files sucessfully but other moment it does not. In both of cases, the Folder Action Dispatcher and System Event process are in memory.

3- No erros in console, the script is very tested, it´s ok.

4- My case the files was not copied.

I use this handle to capture my folder events "on adding folder items to this_folder after receiving added_items"

I have more than a thousands foders with the same script activated.

My problem is: The system does not trigger a folder action script, or the delay is very big.

My system requirements:

OsX Lion 10.7.3

8 GB RAM

well, with a little testing the problem seems to be that the Finder/System Events don't queue up apple events properly. Folder actions seems to be running the script at each invocation but it's not getting picked up by the app at the other end when that app is busy. a delay statement might help, or you might try rewriting the workflow so that it checks every file in the folder, rather than just the ones passed by the folder action.

In reply to twtwtw

25/04/12 20:15:00,171 com.apple.launchd.peruser.501: (com.apple.quicklook.config[6284]) Bug: launchd_core_logic.c:4230 (25397):9

25/04/12 20:15:00,172 com.apple.launchd.peruser.501: (com.apple.quicklook.config[6284]) Bug: launchd_core_logic.c:4180 (25397):9

25/04/12 20:15:00,172 com.apple.launchd.peruser.501: (com.apple.quicklook.config[6284]) Bug: launchd_core_logic.c:4181 (25397):9

25/04/12 20:15:00,172 com.apple.launchd.peruser.501: (com.apple.quicklook.config[6284]) Bug: launchd_core_logic.c:4182 (25397):9

25/04/12 20:15:00,172 com.apple.launchd.peruser.501: (com.apple.quicklook.config[6284]) Bug: launchd_core_logic.c:4189 (25397):9

25/04/12 20:18:07,417 com.apple.launchd.peruser.501: ([0x0-0x35035].com.apple.AppleScriptRunner) Bug: launchd_core_logic.c:4151 (25397):24

25/04/12 20:18:07,418 com.apple.launchd.peruser.501: ([0x0-0x35035].com.apple.AppleScriptRunner) Bug: launchd_core_logic.c:4224 (25397):9

25/04/12 20:18:07,418 com.apple.launchd.peruser.501: ([0x0-0x35035].com.apple.AppleScriptRunner[6869]) Bug: launchd_core_logic.c:4180 (25397):9

25/04/12 20:18:07,418 com.apple.launchd.peruser.501: ([0x0-0x35035].com.apple.AppleScriptRunner[6869]) Bug: launchd_core_logic.c:4181 (25397):9

25/04/12 20:18:07,418 com.apple.launchd.peruser.501: ([0x0-0x35035].com.apple.AppleScriptRunner[6869]) Bug: launchd_core_logic.c:4182 (25397):9

25/04/12 20:18:11,601 AppleScript Runner: CPSGetFrontProcess(): This call is deprecated and should not be called anymore.

25/04/12 20:18:11,665 com.apple.launchd.peruser.501: ([0x0-0x36036].com.apple.AppleScriptRunner) Bug: launchd_core_logic.c:4151 (25397):24

25/04/12 20:18:11,666 com.apple.launchd.peruser.501: ([0x0-0x36036].com.apple.AppleScriptRunner) Bug: launchd_core_logic.c:4224 (25397):9

25/04/12 20:18:11,666 com.apple.launchd.peruser.501: ([0x0-0x36036].com.apple.AppleScriptRunner[6880]) Bug: launchd_core_logic.c:4180 (25397):9

25/04/12 20:18:11,666 com.apple.launchd.peruser.501: ([0x0-0x36036].com.apple.AppleScriptRunner[6880]) Bug: launchd_core_logic.c:4181 (25397):9

25/04/12 20:18:11,666 com.apple.launchd.peruser.501: ([0x0-0x36036].com.apple.AppleScriptRunner[6880]) Bug: launchd_core_logic.c:4182 (25397):9

25/04/12 20:18:15,801 AppleScript Runner: CPSGetFrontProcess(): This call is deprecated and should not be called anymore.

25/04/12 20:18:15,869 com.apple.launchd.peruser.501: ([0x0-0x37037].com.apple.AppleScriptRunner) Bug: launchd_core_logic.c:4151 (25397):24

25/04/12 20:18:15,869 com.apple.launchd.peruser.501: ([0x0-0x37037].com.apple.AppleScriptRunner) Bug: launchd_core_logic.c:4224 (25397):9

25/04/12 20:18:15,870 com.apple.launchd.peruser.501: ([0x0-0x37037].com.apple.AppleScriptRunner[6891]) Bug: launchd_core_logic.c:4180 (25397):9

25/04/12 20:18:15,870 com.apple.launchd.peruser.501: ([0x0-0x37037].com.apple.AppleScriptRunner[6891]) Bug: launchd_core_logic.c:4181 (25397):9

25/04/12 20:18:15,870 com.apple.launchd.peruser.501: ([0x0-0x37037].com.apple.AppleScriptRunner[6891]) Bug: launchd_core_logic.c:4182 (25397):9

25/04/12 20:18:20,227 AppleScript Runner: CPSGetFrontProcess(): This call is deprecated and should not be called anymore.

25/04/12 20:18:46,506 Dock: kCGErrorIllegalArgument: CGSSetWindowListGlobalClipShape: Invalid window 0x7d

25/04/12 20:18:46,506 Dock: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

25/04/12 20:18:46,530 Dock: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Failed

25/04/12 20:18:46,545 Dock: kCGErrorIllegalArgument: CGSSetWindowListGlobalClipShape: Invalid window 0x7d

25/04/12 20:18:46,546 Dock: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Failed

25/04/12 20:18:46,546 Dock: kCGErrorIllegalArgument: CGSOrderWindowListWithOperation

25/04/12 20:18:46,547 Dock: kCGErrorIllegalArgument: CGSOrderWindowList

A overview of my applescript

on adding folder items tothis_folderafter receivingthese_items

set pFileWatchedFolder to copyItems(these_items)

if pFileWatchedFolder is not missing value then speak(ioLib's getDisplayName(pFileWatchedFolder))

end adding folder items to

on copyItems(these_items)

local pFileWatchedFolder

set pFileWatchedFolder to missing value

try

repeat with i from 1 to number of items in these_items

set als_item to item i of these_items as alias

set strItemPath to als_item as alias as Unicode text

set pFileWatchedFolder to ioLib's getWatchedFolder(als_item, pFileWatchedFolder, myWatchedFolders)

if pFileWatchedFolder is missing value then

return pFileWatchedFolder

end if

set this_watched to pFileWatchedFolder as alias as Unicode text

set remotePath to ioLib's getRemotePath(this_watched, strItemPath, myRemoteFolder)

set targetPath to ioLib's getTargetPath(remotePath)

tell application "Finder"

-- verificando se o destino é uma pasta ou um arquivo

if ioLib's isFolder(strItemPath) then

ioLib's attachFolderAction(als_item, path to me asUnicode text)

-- verifica se a pasta existe

if not (exists remotePath) then

set folderName to ioLib's getDisplayName(als_item)

makenewfolderattargetPathwith properties {name:folderName}

end if

if length of (list folder strItemPath without invisibles) > 0 then

set folderItems to (items of entire contents of folder strItemPath)

my copyItems(folderItems)

end if

else if not (exists remotePath) then

-- Copiando o arquivo

if ioLib's isVisibleAlias(als_item) then

copy fileals_item to foldertargetPath

end if

end if

end tell

end repeat

return pFileWatchedFolder

on error errStr

display alerterrStr

end try

end copyItems

------------------------------------------------

------- Metodos Utilitários --------------

------------------------------------------------

on speak(str)

say str & " backup, complete."

end speak

other error found

25/04/12 21:50:17,306 com.apple.launchd.peruser.501: (com.apple.FolderActions.folders) Path monitoring failed on "/Users/Felipe/Projects/Growupge/webapps/examples/jsp/security/protected": Too many open files

????

There are a lot of kind of errors like this, what is the reason ?

Look at the memory usage !!!

Why there are two instance of the same process in memory ?

These dispatcher have not scalability, or it works only for two or three folders ?

This Automator action will handle your problem.

Hi chris if you are running the legacy folder actioin script from a n automator.app "run applescript" workflow node you will need to change the event hander from what you have "on adding folder items to my_hot_action_folder after receiving list_of_added_items .... end on adding items" to that of "on run {list_of_added_items,some_parms} .... end run " I think.

Errors/Run time error log for applescripts - see later in post

If your applescript is solid as far a you know (no run time errors), then you can simply use the automator.app "folder action" workflow using a "run applescript" node only for the folders where you want the applescript event to run.

works great!

You can derive the other envronmentals (folder name etc etc) dynamically from within the applescript. (see my example and others out there)

I just posted this link in reation to another issue that might be of assistance to you. . 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.

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

2) Errors/Run time error log for applescripts: - nope... you will have to develop your own.. especially for backgroud tasks. I developed a simple "logger" that writes to ~/library/logs/my_apple_script.event.log via

do shell script "echo " & console_sysout & " >> " & my_event_trace_log_POSIX

etc etc "and watch with the console.app. you just need to set error recovery environments over all or parts of your script using "try... on error ... end try" constructs.. these are well documented on these and the macscripts.net forums.. so many examples.

In these cases. you need to make your own method of logging stats and errors...

I aev an apple script hat does this and have this in my ~/library/scripts and dynamically load it in the aplescript and pass the text strings to it.. works great.

you could also just use a simple logger via an applescript "do shell" and use a unix log command as somthing really simple .

do shell script "logger " & "\"" & tracefailed_msg & "\"" -- log this to /var/log .. ahs users name attached

hth

Post your results for others to see.

Warwick

Hong Hong