run mode -> per trigger

[coreGreenberet]

Describe the feature

Currently the run modes are per automation, which is fine in most cases, but it is not beneficial, when you are having more triggers which should be looked as their "own" channel

Use cases

Using HA to Sync the state between two integrations:
8 Covers (Warema) with their own API and their counterpart in the "native" House smarthome (loxone).

The warema API will just provide the state "open", "closed" and in % the current state of the cover.
So Warema will report Cover1 open 10%, 20% and the automation will tell loxone "cover.set_position(10)"
Loxone itself sees this as a command to "set the position to 10%" and this will create some kind of loop (especially with some delays in the warema api).
To avoid this -> run mode: restart and put a delay before cover.set_position.
Now is the tricky part: When you open e.g. 3 covers at once -> the first two will be ignored and only the third cover will be updated in the end

possible Yaml:

mode: restart
per_trigger: True

Current workarounds

Copy the automation and exchange the trigger or use a blueprint (but you would still have N automations where N is the count of the triggers), which is 8 in my case

Anything else?

No response