I have a stateless session with a large number of rules most of which set values used elsewhere in the application so looping is a big issue. The rules have been organized into a ruleflows in order to foster orchestration. As a very clean approach to avoid looping (i.e., avoiding adding control to rules) I added an AgendaFilter that tracks the rules that have been fired. Several previous posts discuss that using AgendaFilter's prohibit a ruleflow-group with no activations being detected. Conversely, the API for (de)activating a ruleflow-group seems gone; what is the best way of changing the ruleflow-group from the current group to the one that should execute next (i.e., the next one in the ruleflow)? -- View this message in context: http://drools.46999.n3.nabble.com/Deactivating-ruleflow-group-in-AgendaFi... Sent from the Drools: User forum mailing list archive at Nabble.com.