Rules no longer triggering when multi-homed to another project as of Oct 21

English Forum Tips and Tricks
1

I noticed that the original thread " [Rule keeps moving task back to initial section]" can no longer be replied to. I’m still having an issue with rules, a new issue actually, and wanted to see if anyone else was still having problems. Most of the issues I had with rules had been resolved but starting Monday Oct 21, I have rules that are no longer triggering when a task is multi-homed to a new project.

Here is the scenario:

Project 1 has a workflow where when I move a task to section B it multi-homes the task to Project 2 in section A. Project 2 has two rules in section A that adds a comment and @ mentions some names and a second rule that adds a subtask.

These two rules are no longer triggered when a task is multi-homed into it. The rules ARE triggered if I manually move the task within Project 2 and back to section A.

These rules had been working last week. I tried updating the rules with the work around mentioned in the other thread but that did not fix the issue.

I did try changing the trigger from “When task is moved to a section, section is Section A” to “Task is added to this project”. That did not work either.

What is interesting is that I actually have two similar workflows in two separate projects. The first workflow I built over a year ago so it was using the original rules builder. It never stopped working (so I did not change anything with the rules) while the second workflow which had been built more recently on the newer rule builder did have issues. Now both workflows are having issues with the triggering mentioned here.

1 Like
2

Is the rule set to “Allow this rule to be triggered by other rules”?

1 Like
3

Thank you for your suggestion. No, “allow this rule to be triggered…” had not been selected before when it was working. I can give that a test. I did find a work around in the meantime. I deactivated the rules in Project 2 and instead re-created the rules within Project 1 so they run within the original project. That seems to work.

1 Like
4

I was able to resolve this issue with some help from the Support Team. It was tied to the “Allow this rule to be triggered by other rules” setting. During the issue last week I had turned off this setting for my rules hoping to stop them misbehaving but when the bug was fixed, I learned that this setting had to be turned back on for the rules to trigger with multi-home tasks via another rule. Thanks for responding!