Automater rename issue

Barney already explained why this happens.

Another way around this is to do the folder action in a slightly different way.

Instead of renaming the file outright, first test if the name does not already contain "_PRINT", and only rename the file in case it does not already. This way, the first time a file is dropped into the folder, the script runs, renames the file; this causes the script to run a second time, but this one does nothing, and there is no more loop.

An Automator folder action is triggered by a write operation in the designated folder. The act of dropping a file on that folder is one write operation. Renaming the file in the same folder is another write operation and that will trigger the Automator redundancy that you observe.

What you want is a write-once scenario and then move (rename) the file instance to another folder outside of the drop folder.

Just a quick note to tell you that I have not forgotten this.

I tested an Automator workflow, and it was working when run on its own, but somehow it was failing when used as intended, as a folder action. I will have to go back to it, and try to figure out why it is not working (I am thinking that some security restriction is getting in the way).

Alas, Automator itself does not offer a control flow feature like an "If ... then", so the solution I had in mind is to do this testing inside a script (using either an AppleScript or Shell script action).

I hope to report back with a working solution.

Did you create a folder action?Are you running the workflow on the items added or on all the items in the folder?