Creating an AgendaFilter in stateful sessions is straightforward. Although there are many API's that seem like they would foster discarding /filtering rule activations in stateless sessions, each family of API seems to be missing a key method to filter activations. Can anyone suggest a way that works to filter rules from firing in stateless sessions? Command executors can use FireAllRules on a stateless session, but not with an AgendaFilter. Event listeners can detect rule activation events, but there doesn't seem a way to ignore (e.g., not "accept") an activation. Perhaps this can be accomplished by explicitly disposing of an activation from a listener that detects this, but this approach seems like it could have other consequences. Thanks! -- View this message in context: http://drools.46999.n3.nabble.com/Filtering-activations-in-stateless-sess... Sent from the Drools: User forum mailing list archive at Nabble.com.