I have about a dozen remote web triggers that I use as bookmarks in Safari. I open one of the bookmarks on my iPhone and the macro activates on my Mac. Overall, I'm happy with it.
Until I upgraded to macOS 27.
After the install, and all of yesterday, I was getting random activations of the remote web triggers.
They seem to happen in fairly rapid succession. Music would open. My video player would open up. Volume would be set to mute. The last one would shut down my Mac.
At first, this confused the hell out of me. Then I realized it was behaviors related to my remote web triggers.
My speculation is that either Safari is verifying bookmarks or Siri AI is analyzing bookmarks and activating them in the process. I don't know. Frustration levels are high.
Does anyone else have any experiences regarding this?
Any advice on stopping Safari or Siri AI (or whatever is happening in macOS 27) from accessing these bookmarks?
My current solution is to disable these macros—but that's not a long-term solution.
If your speculation is correct, the problem should stop once the bookmarks have been indexed/processed.
Perhaps disable them all and create a new, enabled, web-triggered macro that just logs a timestamp for every execution to a file on the Desktop. Keep checking that file, and after a couple of days without a new entry start enabling your other macros.
Since the triggers detect anything that accesses the server, if you have them stored as a bookmark in Safari, and Safari decides to access them (to cache the result, to see if they are still valid, whatever), that's going to trigger the macros.
Other than not allowing a browser to have a bookmark, there isn't much you can do to protect against this - its up to the browser what it does with the bookmarks or whether it wants to access them when you aren't explicitly requesting it.
This is a good time/place to remind everyone, that anyone or anything with the Remote trigger codes for your macro can trigger the macros, so always be very careful with what you allow to be done via a remote trigger, and treat them as similar to passwords as far as security goes (depending on what the macro does of course).