Just installed the new beta (2022.11) , and it’s great that only the automations which were actually changed are now reloaded, and not all automatons.
That would remove the need for the automation_reloaded invent added as trigger to avoid it being stopped when you save an automation in the GUI or reload them manually.
However, it could of course be that you edit an automation which was already running (because it wasn’t doing what it’s supposed to) and you want to also retrigger it when that happens (of course you could also wait until it’s completed).
The automation_reloaded event currently doesn’t provide information on which automations are relaoded, it would be great if that would be added. Or otherwise a separate trigger which can be added.
What I can think of as a current work around is to have another automation waiting for the automations to go from unavailable to off and then use automation.trigger on those. But in that case you can’t use things like trigger id and trigger variables in those automations you want to trigger.
