Automations based on this blueprint work fine - except when HA is being restarted during the automation is running. In this situation after restart HA doesn’t know the state of the automation so the finish action will never be triggered.
For my scenarios I live with that, for one important automation (powering off a power plug after usage) I created a „fail-safe“ automation which runs when the blueprint based one doesn’t - which makes the bsleuprint based one basically needless.
The core problem is the missing state persistence for automations which is a HA issue and nothing a blueprint can take care of I think. MAYBE the blueprint can store an information in a helper entity like „input_boolean.automation_a_running = true“ and read that state after HA has been restarted (for this the trigger HA started is available). This way the automation can continue and make sure the finishing action is run. What do you think about this @Sbyx ?