The following info message in the ns.log means that a delay is set on a notification to send when the interval between [some field] and current date becomes less than some value and the date value that is stored in [some field] on the item is already in the past: [DueDateService] -- Due Date event was removed as deprecated
# trigger set to email someone every time a promotion was executed # # would send 1000 emails if there were 1000 files in the project. # This event trigger will only send one.
Date only fields do not work correctly when used in certain notification rules. The following notification rules only send when DateTest ( date only field ) is set to tomorrow's date and will not send when it is set to today's date :
If it does, it sends an email (if that's the action required for the notification). In a "Due Date" scenario, there is no change being made to the item; the only change happening is time passing, which doesn't cause anything to be written to the Change History table. If a change is made to the item, the rule will then check the date and send email if the date is passed, but the change to the item may not happen until long after the due date .
update TS_NOTIFICATIONEVENTS set TS_TIME=2000000002 /* date from distant future */ where TS_DELAYED=1 and TS_TIME=0 and TS_ID < (select TS_LASTID - 100 from TS_LASTIDS where TS_NAME = 'NotificationEvents');
Notifications will send out repeatedly every time the notification server cycles (usually every 5 minutes) if the TS_NOTIFICATIONEVENTS and TS_NOTIFICATIONMESSAGES tables are set to cache into memory. Restarting the Notificaion Server will stop the messages, but as soon as more notifications are generated, the new messages will repeat.
