I've been seeing this behavior pop up every once in a while where a very old alert from a client pops up about two+ months after it has occurred. What is even more odd is that the same event has been previously logged under a different ID but if you look at them the trigger time and threat are identical. You can see they have identical time-stamps for the occurrence and threat types, yet unique ID numbers and a report dates 3 months apart. I can't really tell if this a client-side issue or a server-side. Anyone have an idea?