This trigger shouldn't fire on actions or conditions with exception path, as it must be possible to override the trigger, nor should it fire as result of an exception if the currently executing flow obtained control by exception trigger already, to avoid responding to a double fault condition.
Trigger should, among other, provide name of the flow causing the exception, and probably all variables which are available after exception anyway.
Allowing choice of flows (or wildcard) to fire the flow may be practical.
Such a trigger will help reducing the amount of literal red tape in many flows - see screenshot example:
- redtape.png (98.68 KiB) Viewed 9363 times