Many automator actions failing since Mavericks

I'm having a lot of issues as well, mainly in "Watch me do" actions (clicking buttons on applications in my case). They are all failing now. I even tried creating a new one, which works flawlessly when I run it from automator, but fails every time "Automator encountered an error with Watch me Do action" when it runs on its own. Really frustrating.

Same here. I have a workflow action that moves all photos from Photostream into a folder where Lightroom picks them up. Since Mavericks, the photos are not being moved.

All my "watch me do" actions are failing since Mavericks are well. I'm getting the exact same error as nvrmore100 wrote he is getting.

Similar to the above.

• Applescript working fine when run within automator but fails when run "as application"
• Old "watch me do"s not running ---> rerecorded
  • Some rerecorded ones working within automator but fails when run "as application"
  • Some rerecorded ones not even working within automator

As a test I tried the following:

• Created a "watch me do" using record but taking no action (i.e. a blank "watch me do") --> fails as application
• Created a "watch me do" consisting of opening system preferences and closing it again ---> fails as application
• Created a "watch me do" using the automator-->utilities--->Watch me do (no actions)--> fails as application

Anyway glad it's not just me.

same here. some of my AppleScripts within the flows have started returning blank results which is unexpected.

mine turned out to be related to the svn command i have in my scripts. Looks like scripts were ignoring the my exported $PATH values and trying to use the newer version of svn

Same here. I had a workflow with a keyboard shortcut to launch my favourite iTunes playlist. I does not work since the update to Mavericks EXCEPT when I run it from Automator. This is a regression.

Same problem and I haven't been able to find anything else on it other than this post.

Any clues would be appreciated. For now all the things I built in Automator are manual.

I've got my automator app up and running again.

I made a new automator app, and changed some settings (security & privacy settings). In my case, the app i made is "Adsolut", so i ticked it on.

A little challenge for you guys, since i don't know the menus in english, so here you go with the finnish screenshot 😉

😕 Perhaps i was too happy too quick.

i made this cool app i needed everyday, and got it working just fine. Then i decided to adjust the "watch me do" mouse speed just a little bit, and boom - the app stopped working 😟

One more post... When an app says it encountered a problem, I opened the security & privacy settings, took the tick off and put it back on. Miraculously the app started working.

Enabling access for GUI scripting is on a per-application basis in Mavericks. Each individual application will need to be added to the Accessibility privacy list or granted access via the dialog(s). Note that altering the application (such as changing the Watch Me Do scripting) will cause the system to see it as something different, so the process will need to be repeated for the new application. See Apple's support document http://support.apple.com/kb/HT5914 for more information.

Ugh thank you!!! I never even thought about looking at accessiblity security, yet I had a bunch of other things that use it and had to give them access also. Thanks, this fixed my issue!!

I have used Automator with ARD to do a lot of clean-up tasks in my lab, including deleting the files on the desktops of the remote computers. It used to work fine with Mountain Lion, until I updated to Mavericks.

The Automator script that is failing is this:

osascript -e 'tell application "Finder" to delete every item of the desktop whose class is not disk'

The error that is reported back to ARD is this:

Error: 1 "29:85: execution error: Unknown object type. (-1731)"

Any ideas on how to fix this?

Try:

everyitemofthedesktopwhereitsclassisnotdisk