When the user changes a configuration parameter then all rules that use that parameter are re-run, they are simply added to the job scheduling system and as soon as they're completed they inform their listeners of the new Result. This means that if a currently running job isn't cancelled then the result that becomes stored and displayed is that of the evaluation that is last to finish. So if the user has a long running HotMethods evaluation that they wish to configure to be quicker by increasing the sliding window size then that new evaluation risks completing faster than the old running one, which means that the result based on the old configuration will be the one reported.

This isn't that bad in this case, but with other rules being used in JMC this could become an issue.