Describe the current behavior
When creating an automation with a trigger that listens for multiple state events like below, it can suggest that this automation would trigger if the flow run were to be stuck in any of the states for the duration specified.
What happens instead is that the PENDING event creates a bucket.Then, it sees the RUNNING event and increments the same bucket, invalidating the bucket because of both being listed in after. What would be needed here is composite trigger instead.
Describe the proposed behavior
A way to inform users of how their automations will trigger and/or a way to create compound triggers in the UI.
Example Use
No response
Additional context
Related: #16545
Describe the current behavior
When creating an automation with a trigger that listens for multiple state events like below, it can suggest that this automation would trigger if the flow run were to be stuck in any of the states for the duration specified.
What happens instead is that the
PENDINGevent creates a bucket.Then, it sees the RUNNING event and increments the same bucket, invalidating the bucket because of both being listed inafter. What would be needed here is composite trigger instead.Describe the proposed behavior
A way to inform users of how their automations will trigger and/or a way to create compound triggers in the UI.
Example Use
No response
Additional context
Related: #16545