Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Applescript in Automator behaves differently when executed from inside Automator, or as an Automator application

Hello everyone,


I'm trying to execute an Automator workflow at startup, which I do by saving the workflow as an application, and adding it to the startup list, this works fine.


My workflow works fine when executed from within Automator (ie clicking on the "Execute" button), but does not anymore when the Automator application is executed (ie. simply double clicking on my Automator file)

I have narrowed it down to an Applescript inside my workflow which fails only when the application is executed from the finder (the step works fine from within Automator). The script automatically creates an ad hoc wifi network.


The line which specifically fails is :

set menu_extras to value of attribute "AXDescription" of menu bar items


Anyone has any idea why executing the workflow from within automator, and executing it from the finder yield different results ?


The crazy thing is that all this worked fine up until a few days ago, there might have been an update since (running Mavericks 10.9.2), but nothing game-changing.

MacBook (13-inch Late 2009), Mac OS X (10.6.8)

Posted on Apr 12, 2014 11:32 AM

Reply
1 reply

Applescript in Automator behaves differently when executed from inside Automator, or as an Automator application

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.