Well, dang it. I’m foiled again. If it was a bug, I could have hoped for a fix. But if by design, this approach to effectively manually run an automation has been foiled.
I recently posted a discussion inquiring about forcing automatons to run, as I could do with routines in the Classic App, but as that discussion concluded, you cannot. Well, not natively. With WebCoRE you can. I haven’t graduated to that level yet.
So my hope of using scenes as the actionable Then statement of the automation seemed the perfect solution, given scenes are able to be run manually on demand.
But foiled again…
Is there no native way to get where I’m trying to go in the new app?