000017876 - Digest Notifications not sending: Daily  Weekly  Monthly  Quarterly - RSA Archer

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000017876
Applies ToNotifcations not being sent
RSA Archer

Normally, when you save a record and there is a digest notification associated with the record, an entry will be created in tblNotificationTemplateContentQueue with the create_date matching the last updated date time on the record.

When the notification is sent, the table is cleared of associated entries and the process begins again.  If for some reason the notification faults the table is not cleared and the entries create_date changes to the time the notification was scheduled to run. 

Some systems will not have enough memory to process large numbers of content record in a digest email and it fails.  This causes the system to recycle all of the existing content record and any new ones for the next notification cycle and it fails again.  Clearing the table and creating a more efficient notification is in order.

IssueDigest Notifications not sending: Daily, Weekly, Monthly, Quarterly 
CauseA secondary cause could be that records are not being updated by being Saved or Applied. Digest notifications are _NOT_ sent when field values are recalculated, but only when being Saved to the database. Verify that records are actually being Saved/Applied when using a digest notification, otherwise you must use Data Driven Event generated Notifications.

The best way to clear this table via the User Interface is to copy then delete the notification.  It is possible to delete the entries directly in the database however, this is a last resort and should be avoided if possible.  

      Select* from tblNotificationTemplateContentQueue where notification_template_id =


      Select* from tblNotificationTemplate where template_name =

Legacy Article IDa65598