It's currently possible to manually trigger an Automation to run if the defined trigger event is a Schedule and if the workflow is currently running. (You need to select the Schedule item in the workflow and then click the Trigger button at the bottom of the parameters window.)
It would be great if the option to trigger an Automation could be extended to all types of Automation trigger events so that they could be triggered from within the Automation interface, and so that the process could be made more consistent.
For example, you can't currently trigger a topic subscription from within the Automations interface. For that you need to save the Automation and go to the Notifications page and fire the Topic from there. I haven't checked the directory watch and similar trigger events but suspect them to be the same, i.e. needing to perform an external action to trigger the event.
Additionally, I've noticed that triggered automations do not get listed in the triggered jobs history until the automation job has completed. It would be good to see them listed as soon as the Automation is triggered (perhaps with an "Incomplete" Status and no finish datetime). Today I was testing firing a topic to trigger an automation and did not know it was working as the job wasn't showing up in the job history, so I inadvertently triggered multiple jobs...
These ideas tie back to this question:
Merged Ideas:
On Demand Automation Option by robotix on March 31, 2020
On Demand Automation Option
-I don't want to stop, it go into the schedule, adjust it and restart it
-I don't want to go to the job log and resubmit
-No, I don't mean workspaces. I know you can do that.
-Just right click Run Now..???
-Actions: Run Now ???
Thanks. Have a nice Day.
