When setting up automations, are automations triggered by the union or intersection of flow run tags?
e.g., given automation with flow run tags
production
,
auto-scheduled
, should we be expecting it to run for any flow tagged
production
, or only those both
auto-scheduled
and
production
?
It appears to be that either tag will trigger it, which is not what i was aiming for
✅ 1
c
Christopher Boyd
02/07/2023, 12:40 PM
So you’re looking for an AND , not an OR criteria?
m
Mike O'Connor
02/07/2023, 2:20 PM
yeah - only want to be notified on a combination of tags, not OR.
w
Will Raphaelson
02/07/2023, 4:06 PM
Thanks for that feedback @Mike O'Connor - we’ll likely expand the sophistication of triggers in a few different ways on the 2-3 month timeline, so i’ll incorporate this input into those decisions. In the short term, unfortunately I think you’d need to hack around this a bit, perhaps concatting the tags into another tag and configuring the trigger to fire on the presence of that new tag.
m
Mike O'Connor
02/07/2023, 4:09 PM
yeah right now i have an alternative tag which reasonably represents the combination so it’s not a blocker, thanks!
j
James Ashby
04/28/2023, 7:34 PM
Just want to thrown in my vote that this feature would be very useful!
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.