I'm not sure, but it could be that your rules (which is really just one rule) belongs to the same rule-flow-group. So, when the first rule node is executed, the rule-flow-group is activated and the rule get fired. When the second rule node is executed (in the second iteration of your multiple-instance), the rule-flow-group is activated again (actually, it was already active), but since anything has changed since the last execution, no rules will be fired. One possible solution could be to add a "guard" restriction to your rules. So, inside the subprocess you can insert an instance of this "guard" object before the rule node. You can also even have a rule with low salience to retract this "guard" when you are done. Best Regards, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Esteban Aliverti - Developer @ http://www.plugtree.com - Blog @ http://ilesteban.wordpress.com On Wed, Jun 1, 2011 at 6:31 AM, HMandic <trbuhom(a)net.hr&gt; wrote:

Yes, I was talking about a dummy object that must be inserted before the Rule Node. Your rules then should use this object at its first restriction, but there is no need to modify it. Ej: when Guard() .... then .... end The low-salience rule I was talking about is meant to clean up the session. Best Regards, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Esteban Aliverti - Developer @ http://www.plugtree.com - Blog @ http://ilesteban.wordpress.com On Wed, Jun 1, 2011 at 10:00 AM, HMandic <trbuhom(a)net.hr&gt; wrote:

It would be "polite" to have it: Rule "Cleanup Rule" salience -999 rule-flow-group "your group" when $g: Guard() then retract($g); end The low salience will make activations of this rule to be executed at the end of the execution cycle. Best Regards, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Esteban Aliverti - Developer @ http://www.plugtree.com - Blog @ http://ilesteban.wordpress.com On Thu, Jun 2, 2011 at 5:34 AM, HMandic <trbuhom(a)net.hr&gt; wrote: