Quote:
Originally Posted by dnanian
The only problem here is that you've run two jobs but only one can run at a time - and "run using settings" does not block. If you set things up as in the FAQ, and run the little program rather than directly running the settings, you'll leverage our "schedule driver", which knows how to queue the jobs, mount and unmount drives, etc.
|
But the jobs aren't running concurrently, they're running sequentially. Automator triggers the first job which fires off the shell script triggering the second job once it's done. It worked for me, but maybe that was a fluke.
To do as the FAQ instructs, you'd replace my step #3 with the instructions in the faq...
http://tinyurl.com/ljv8pz
... and point the shell script to the resulting app from the FAQ instead of the automator "Max" job in my example step #4.