Re: [rules-users] 5.3.0 CR1 has broken existing rules/flows

Thanks for all of the feedback. I haven't tried W's handler, but I'm planning to. I did take Edson's advice and was able to get some more info. It appears to involve the interaction between 3 rules. For background, this is a fraud detection application. Under certain conditions, we need to look up additional customer information. Some rules are run to determine whether the lookup is required and then another rule actually does the lookup. In this case: Rule 021 says if the order is small, set the lookup flag to false Rule 042B says if the order is from a 'bad' country, set the lookup flag to true Rule 022 says if the lookup flag is true, do the lookup If rule 021 fires alone, then 022 does not fire and all is well. If rule 042B fires alone, then 022 fires and all is well. If 021 fires to turn off the lookup AND 042B fires to turn on the lookup, then 022 gets and NPE. As Edson suspected, the item is null and the 'rule' variable points to rule 021. I'm not sure if it matters, but each rules involved is in a different agenda group. As I mentioned, this works in 5.2.0.Final, but breaks in 5.3.0.CR1. Hope this helps pinpoint the issue. -- View this message in context: http://drools.46999.n3.nabble.com/5-3-0-CR1-has-broken-existing-rules-flo... Sent from the Drools: User forum mailing list archive at Nabble.com.