0

How can I stop Automator using previous specification for my actions?

I’m going crazy with Automator. I have three folders : Deployed, Draft and Live.

In both folders there is a Public folder:

Before

I want to use a set of Automator actions to: Copy the Live Public folder to the Deployed folder, then rename the copied folder by suffixing the date to it. Finally, copy the Draft Public folder to the Live folder

Seems simple. But, Automator seems to remember the previously specified location of my Public folder and applies my action to both the previous specification and the new specification.

Here is the set of actions:

Script

Here is the result, with the Draft being copied to Live, as I wanted, BUT with the renamed Public folder from Deployed also being copied back to Live :

After

Can someone put me out of my misery? How to I stop it using the previous specification? Is there a clear option for memory or another approach - I have tried many.

Thanks.

1 Answer 1

0

Each action passes an output to the next item. So your action to Rename Finder Items will pass its output on to the next action.

You need to check "Ignore this action's input" when you Get Specified Items for the second time.

2
  • Excellent - thanks for that.
    – Colin
    Apr 30 at 15:22
  • 1
    @Colin Then please mark it as the answer.
    – benwiggy
    Apr 30 at 16:59

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .