Thank you for the pointers. My understanding is that since it is failing on the construction heuristic (move/unmove not used at this point) then the issue would be in the score rule?
Here is my only score rule (ShiftAssignment is the only planning entity with shiftStartTime/shiftEndTime changing). Maybe something would jump at you: rule "intervalRequirementCovered" when $intervalReq : IntervalRequirement($interval : interval, $position : position, $staffingRequired : staffingRequired) $matchingShiftAssignmentsCount : Number() from accumulate( $matchingShiftAssignments : ShiftAssignment(shiftStartTime <= $interval, shiftEndTime > $interval, position == $position), count($matchingShiftAssignments) ) then insertLogical(new IntConstraintOccurrence("intervalRequirementCovered", ConstraintType.NEGATIVE_HARD, Math.min($matchingShiftAssignmentsCount.intValue() - $staffingRequired, 0), $intervalReq, $position)); end Thanks, Guy -- View this message in context: http://drools.46999.n3.nabble.com/Planner-5-3-Final-presumedScore-is-corrupted-when-using-update-on-the-rules-working-memory-tp3546932p3550542.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users