Change Details

Since tagging of actions which hit the condition limit is enabled, I've only seen it hit by mass actions, specifically MassMessage delivery and Nuke. I'm not sure about why this happens, but I'm not sure that we should keep this going. I imagine it may be because those actions perform "all actions at once", so for instance AF may count all those actions as a single one (so conditions get summed up and of course break the conds limit). Anyway, we should probably find a way to avoid this behaviour, since it only clogs logs of condition limit reached.

Since tagging of actions which hit the condition limit is enabled, I've only seen it hit by mass actions, specifically MassMessage delivery and Nuke. I'm not sure about why this happens, but I don't think we should keep this going. I imagine it may be because those actions perform "all actions at once", so for instance AF may count all those actions as a single one (so conditions get summed up and of course break the conds limit). Anyway, we should probably find a way to avoid this behaviour, since it only clogs logs of condition limit reached.

Since tagging of actions which hit the condition limit is enabled, I've only seen it hit by mass actions, specifically MassMessage delivery and Nuke. I'm not sure about why this happens, but I'm not sure that don't think we should keep this going. I imagine it may be because those actions perform "all actions at once", so for instance AF may count all those actions as a single one (so conditions get summed up and of course break the conds limit). Anyway, we should probably find a way to avoid this behaviour, since it only clogs logs of condition limit reached.