How do I identify what script/automator app is causing me to repeatedly get the error 'The application “ScriptMonitor.app” is not open anymore.'

Question

Level 1

17 points

How do I identify what script/automator app is causing me to repeatedly get the error 'The application “ScriptMonitor.app” is not open anymore.'

I got a new computer to replace an old/slow mac mini and I restored it to the new computer via backup. I have a lot of scripts that run automatically via numerous node-red flows. I understand that this error comes from automator apps and/or applescript apps and that they need to be re-saved as new apps. The problem is: how do I identify what scripts need to be re-made and where they are? These are old scripts and I don't have them all in 1 place.

BTW, this is a very uninformative error... I wish it would at least give me an actual script name.

Mac mini (2018)

Posted on Aug 19, 2023 10:59 AM

Reply

Answer 1

Top-ranking reply

James Brickley

Level 5

5,692 points

Aug 24, 2023 6:38 PM in response to hepc@72

It's definitely one of your Automator scripts, likely written prior to newer Automator security features were added. The script is being blocked as a result.

Check if you have these scripts set to run at login. On Venture go to System Settings -> General -> Login Items. They should be in the 'Open at Login' list at the top. Right-click the script in the list box and choose Show in Finder. Then open the script in Automator and save it.

If you used launchctl to create agents or daemons to run the scripts then look in ~/Library/LaunchAgents or /Library/LaunchAgents or /Library/LaunchDaemons. See if you have any scripts being started that way. These should show up in the Login Items in System Settings under Allow in the Background. If you have Xcode installed it can read those PLIST files. Otherwise you can use a programming text editor to read them. They are basically XML files. Something like the free Microsoft Visual Code Studio would be fine.

Another place to look would be the much older ~/Library/StartupItems there should be nothing in that location. Check to ensure you don't have a /Library/StartupItems either.

Reply

Answer 2

Aug 24, 2023 9:15 PM in response to hepc@72

Unfortunately, it will be a process of elimination. Or you could go the brute force method and open every single Applescript or Automator script and re-save all of them.

Root cause was upgrading from an old macOS to a newer macOS which added security features to protect against malicious Applescripts and automations. Much like Windows has to protect against PowerShell scripts.

With such a complex setup, migrating to a new Mac can be maddening. Best practice would be multiple backups and slowly migrate things over more individually versus running the Apple Migration Assistant and moving everything at once. It's fine for basic users but not so good for the power users who push the limits with complex configurations. Certainly, you are running more automation than 99.9% of Mac users.

Reply

Answer 3

hepc@72 Author

Level 1

17 points

Aug 24, 2023 8:11 PM in response to James Brickley

Knowing where to look isn't so much the problem. I have lots of scripts. Most of them run via node red. There might be some that are run via cron job and there are some that are quick actions. The problem is knowing which ones are causing the issue.

You seem to suggest that it's specifically an Automator workflow as opposed to an AppleScript. I have fewer of those, but most of them are quick actions and are not run automatically.

Honestly, this "feature" is a big pain in the neck. Why couldn't they have come up with more helpful error messages?

Reply

Answer 4

hepc@72 Author

Level 1

17 points

Aug 25, 2023 6:58 AM in response to James Brickley

Incidentally, the reason this particular Mac was pretty far behind in macOS versions was because I had a 32 bit app that I relied on to interface with a dongle for quite some time. The company that made it got bought out and they produced a 64 bit version that I tried out, but it was really buggy, so I kept on using the 32 bit version, which I think meant I was stuck at Mojave. I eventually replaced the dongle for another product that had some plusses and minuses compared to the old one, but once I got used to it, I finally decided to retire the old one.

I'm all about security updates, but IMHO, if you create features and continue to maintain them, the transition from one OS to another should not break things. At the least, make it a smooth transition for users. Otherwise, you're sending a message to users that you don't care about them. It shouldn't matter what percentage of users use that feature. If you provide that feature, then support it and keep it healthy. It shows you take pride in your product and it tells users that your products are dependable and that will engender brand devotion. Apple used to do that. In fact, it was part of the dogma. Things "Just work". That philosophy has been continuously eroding for quite some time.

Reply

How do I identify what script/automator app is causing me to repeatedly get the error 'The application “ScriptMonitor.app” is not open anymore.'

Similar questions