[ https://issues.jboss.org/browse/DROOLS-1347?page=com.atlassian.jira.plugi... ] Matteo Mortari edited comment on DROOLS-1347 at 10/28/16 11:01 AM: ------------------------------------------------------------------- With reference to [DROOLS-311]. This issue [DROOLS-1347] is assuming the previous behavior of expiration (as behaving before 6.5.0.Final), which has now been fixed to align with design requirements {quote} 1. Expired events does not cancel rule activations {quote} Hence, with [DROOLS-311] now fixed (from 6.5.0.Final), when the clock is advanced a second time, the expired event is still given the chance to match (as required by design). Not a bug. Not a regression. was (Author: tari_manga): With reference to [DROOLS-311]. This issue [DROOLS-1347] is assuming the previous behavior of expiration, which has now been fixed to align with design requirements {quote} 1. Expired events does not cancel rule activations {quote} Hence, with [DROOLS-311] now fixed, when the clock is advanced a second time, the expired event is still given the chance to match (as required by design). Not a bug. Not a regression. -- This message was sent by Atlassian JIRA (v7.2.2#72004)