Hey y’all!
I’m running into a strange problem where a multi-select custom field is causing for loops based on the total count of selected options.
The field is a selector for marketers to choose tactics they’d like to deploy. Upon selecting a tactic, a sub-task will be generated and assigned to the appropriate tactician.
The issue is when the list is modified. Say a member chooses tactic 1, tactic 2, and tactic 3. In an ideal state, subtasks for the respective tactics will be generated. Sometimes this works properly.
However if the marketer goes back and selects tactic 4; instead of adding a new sub-task for the fourth tactic, 4 tactic 1 sub-tasks will be created.
This behavior also happens if a tactic is removed from the list.
I believe the issue stems from the new rule builder where the only trigger criteria is “custom field is changed”. At any point of the custom field being changed, an extensive evaluation of tactics is completed. Naturally, if the element matches, the sub-task gets created, regardless if the sub-task has already ran. This repeats itself for the count of total tactics selected from the list. Upon hitting the first tactic in the list, it’ll create the sub-task and repeat.
I’m wondering if anyone has a similar experience and if there are any suppression rules that could be implemented to limit this? I’ve tried bulking the tactics + rule creations into a single rule. I’ve also broke them into separate rules.
My only thought would be to create single select fields for each tactic, having the automation changed to: if multi-select contains, turn the static single select boolean to “True”, and create the sub-task off that single select field. This would work because once the boolean is true for a tactic, there’d be no intervention to revert it back to False. The issue with this is that there are over 20 potential tactics; and this would create unnecessary clutter in the form of custom fields.
Note: I’ve had this issue with both Bundles and project instantiated rules.
Any help would be greatly appreciated!
Thanks so much,
Taylor
