Automator workflow fails to run on terminal, but runs from within automator. Why

automator

I created an automator workflow and saved it as a workflow. When I test it from within automator, the workflow works. But when I try to run it from the command line (automator path/to/workflow), I get the following:

No application name for definition at URL file:///Library/Automator/Office.definition/

Failed to load definition at URL file:///Library/Automator/Office.definition/

No application name for definition at URL file:///Library/Automator/Office.definition/

My ultimate goal was to run this workflow with Lingon, so that I can schedule it. (Lingon throws the same errors).

I also tried saving it as an application and then running the Application Stub, but I get the same errors.

What am I doing wrong?

Update:

Here's the screenshot of the actual workflow.
enter image description here

Best Answer

I made an Automator workflow, using the Actions shown in your screenshot, and saved it as an application named CopyFiles.app in the /Applications folder. In Terminal I typed open -a CopyFiles then pressed enter and it ran as expected creating a copy of the files to the designated location.

Next, using Lingon X, I created a new Launch Agent to run the open -a CopyFiles command at a set date and time, so I could test that it works, and it triggered at the set date and time and copied the files to the designated location, as expected.

Related Question