Specifying the Notification Expiration Age
For each notification class, you can specify an expiration age for notifications. This topic discusses how Notification Services uses the expiration age and how to configure the expiration age.
Notification Expiration
When a subscription rule produces a batch of notifications, the batch has a creation date and time. If the content of those notifications is time sensitive and should not be delivered after a certain period of time, you can specify an expiration age.
Every time the distributor attempts to deliver work items from the notification batch (on the first attempt as well as on retry attempts if there is a retry schedule), it will first check to see if the notifications have expired. If they have, the distributor marks the work item as expired and does not attempt to format and deliver the notifications, regardless of the retry schedule. If you do not configure an expiration age, the notifications never expire.
Important
If you have not provided retry schedules for delivery protocols, the distributor does not retry delivery. For more information, see Specifying Delivery Protocol Execution Settings.
To specify the notification expiration age
- If you are defining an application through XML, define the notification expiration age in the ExpirationAge Element (ADF).
- If you are defining an application programmatically, define the notification expiration age using the ExpirationAge property (NMO).
See Also
Concepts
Defining the Notification Schema
Configuring Content Formatters
Specifying Digest or Multicast Delivery
Specifying the Notification Batch Size
Other Resources
Defining Notification Classes
Defining Notification Services Applications
Defining Notification Classes
Configuring Delivery Protocols