This was seen using 6.x-1.x-dev 2011-Sep-15 version.

The code is not clearing the cache between notifications.

Example:
I have three clients (A, B, and C). I also have three Users (1, 2, and 3) that need to be notified of the separate cases that only they are responsible for when a new case is over 1 day old. The problem as I am seeing it, is that as the notifications are generated, the resulting emails continue adding cases to the original query.

Each client submits one case and the time elapses to force notification emails to be sent. This happens when all or several notification are triggered at the same time.

Support Nag generates the first notification email to User 1 for Client A. Only cases for Client A are listed in body of email text.

Support Nag generates the second notification email to User 2 for Client B. Cases for Client B and Client A are included in body of email text.

Support Nag generates the third notification email to User 3 for Client C. Cases for Client C, Client B and Client A are included in body of email text.

If a Nag Rule has multiple Clients assigned and if it is at the top of the list, then all clients that are part of that rule are included in all other emails that are part of that execution of Nag at that time.

I did find a work around for my situation, but it is not a guaranteed long term fix. If I stagger the times of when each Nag rule is run, (I changed the times using phpMyAdmin) so that each of the rules are at least one cron cycle apart, then the Nag notifications are correct. If your cron schedule is such that it only runs a couple of times a day and you have several Nag rules, then it becomes possible for the LAST RUN times to re-align and the problem to re-occur. As long as each rule runs at a different cron cycle, the problem of extra clients does not present itself.