Marshall Broussard

I have a quick wrapper condition/action that you can put into practice currently. It is a useful concept to keep in mind when running any kind of automated actions such as these. This will also allow you some flexibility in only allowing some triggers to hit the "off switch" or also allowing you to decide which triggers do and don't follow the "off switch". With that, and proper implementation, you can avoid all of the concerns as mentioned above. 

There are two parts to the wrapper, and the first is to simply put a mandatory condition that states "Ticket must not contain the following tags (automation flag)" and then an action at the end of the trigger to add the (automation tag) to the ticket. That way, when the trigger closes, and the system re-checks all triggers, any trigger that has been configured to ignore tickets with the (automation flag) tag will not fire. This will also allow you to make triggers that will ignore the (automation flag) tag or that do not set the tag when they complete. This does add a layer of complexity to the rule architecture, however it is wildly easier to manage than to go one by one and check each trigger's conditions and actions and manage an ever growing cascade of triggers.