Hi, When we set 3 overdue notices in the Overdue notice/status triggers tool, delay depends on the due date. But if a user has a couple of overdue documents, the notices sent take all of the documents without taking the delay into account. I have 3 triggers set, the first overdue notice (odue1) is set to be sent after a delay of 1 day, the second overdue notice (odue2) is set to be sent after a delay of 7 days and the third one (odue3) after a delay of 21 days. In each of the notice's body I have items informations like title and author between html tags(<Item><Item/>). Let's say I have one document due on september 1st (Harry Potter) and one due on september 10 (Lord of the Ring). On september 2 odue1 is sent and in the message body it says "Your document : Harry Potter is overdue, bla bla bla" On september 8, odue2 is sent for Harry Potter with the right message "Your document : Harry Potter is overdue, bla bla bla". But, on september 11 an odue1 is sent for Lord of the Ring, but the message body it also mentions Harry Potter even tho we are way past the 1 day delay, at that point we are at 10 days. "Your documents : -Harry Potter -Lord of the Ring is overdue, bla bla bla" On september 22, odue3 is sent for Harry Potter and also mentions Lord of the Ring even tho at that point LotR has only been overdued for 12 days. So, it seems that overdue_notices.pl takes all of the overdue documents in an user account and add those document's informations even tho they are not concerned by the trigger delay.
Hi Noemie, how is your cronjob for overdues (overdue_notices.p) set up? I'd expect the behaviour you describe if it's run with the --list-all option. Could you check? In that case it would be correct and if you don't want other items listed, than removing the flag would be the first thing to try.
Hi Katrin, Thank you very much, I didn't know about this flag. All our sites have the same cronjobs with the same flags so it makes sens the behaviour is the same everywhere for us. We'll try to remove the list-all flag. Thank you again
The tests confirmed that it was indeed the flag that caused the problem. Thank you!