Odd behaviour with automator workflow

Get help. Get answers. Let others lend you a hand.

Moderator: Mr_Noodle

Odd behaviour with automator workflow Wed Jul 02, 2014 3:29 am • by scrabble
Hi there, i have a rather simple setup which causes a strange behaviour. It's two part, first a hazel rule, second an automator workflow:

Hazel-Rule
======
If all conditions are met:
- kind is archive
- name is xyz
- modified is not in the last two minutes
then
- run automator workflow

Automator workflow
=============
- New mail message (with some text)
- Get specified finder items (points to the xyz-archive)
- Add attachments to front message

It's the last step I can't cope with: Running the whole workflow as described I have two attachments of the xyz-archive in my mail. I have modified the automator workflow by omitting the last step and the whole workflow runs fine. Obviously omitting "add attachments to front message" sould make no sense.

So my question: why doesn't act the complete workflow (with the original automator workflow) as expected. And why does the incomplete automator workflow make sense here?
scrabble
 
Posts: 7
Joined: Tue Aug 30, 2011 4:30 am

Re: Odd behaviour with automator workflow Wed Jul 02, 2014 2:27 pm • by Mr_Noodle
You shouldn't be asking Finder for items. The file being processed is passed in to the workflow so just make sure the first item in the workflow takes a file as input.
Mr_Noodle
Site Admin
 
Posts: 11866
Joined: Sun Sep 03, 2006 1:30 am
Location: New York City


Return to Support