When you have multiple branches in a rule (check if conditions), the rule will run each branch one by one in the order built. If it doesn’t find check if condition 1, it will move to check if condition 2 and so forth.
I need rules to run in multiple check ifs. This means, when rule runs and check if condition 1 is met, trigger 1 action. AND when rule runs and check if condition 2 is met, trigger 2 action as well, and so forth. Right now, this is not possible and forces me to build multiple rules separately, which makes is impossible not to reach the 50 rule cap.
1 Like
I have been able to do something similar with a single-select custom field for the rule’s status as long as I don’t run up against the branch number limit.
At the end of each branch, I add an action to set the custom field [Subtask Rule Trigger] to the next value.
I then set a trigger for changes to that field [When “Subtask Rule Trigger” is changed] , and use the value from the field as part of the conditions for the next step, basically forcing the rule to run as a controlled loop.
It does still run each branch one at a time, in order (necessary in my case), but has let me take action in each branch, combining what would have been multiple rules into a single rule.
@Andrea_Gils_Monzón,
The title of this topic doesn’t really match the request text, I don’t feel.
It sounds like you want “check ifs” that are not mutually exclusive as they are now, right? (Not that you need rule action to run simultaneously, which they actually already do in some circumstances.)
Can you give the actual use case (or a simpler one if complex to explain) that would demonstrate your need so it’s more clear?
Would use of a multi-select custom field help? That offers some more flexibility in the “check if” conditions you can write.
Thanks,
Larry
Hi @Andrea_Gils_Monzón,
While not perfect, one way around the 50 rule cap is to have a check if condition trigger adding the task to an additional project where another set of rules live. That project can apply up to an additional 50 rules to the task.
1 Like
Thank you :)! Work-arounds are helpful, but I’d love to see this cap lifted to avoid unnecessary projects being created. Not sure the rationale behind the cap beyond keeping things more manageable. Would be helpful to know why.
To clarify this post, I’m looking to have these rules run all at the same time. Currently, if I build branches with check ifs for each one, the rule will only run on one branch and not all simultaneously. So if the rule finds 1st branch to be true, it doesn’t keep running.
I have 10 rules set up this way, instead of 1, which eats up my quota.
The field is multi-select. Does that make sense?
