Benedict, > Thing is, what is causing the nan?
My guess is that a NaN somehow got into your AWL database. I have reopened bug 3364, and attached a richer patch: "Deal with NaN in AutoWhitelist and PerMsgStatus" which includes my previous patch and also instruments AutoWhitelist module to check for NaN on data entering or leaving a database. It should produce warnings and ignore such data. Please try it. Mark
