Notification History

    Notification History is the record of every email and SMS notification ManageEngine SecureAI has attempted to send. Use Notification History to confirm communication requests, approvals, and scheduled tasks. Notification History will also determine where a notification attempt was halted. .

    How it works

    SecureAI creates an entry each time it attempts to deliver a notification, not when you define one. Every module that uses Notification Templates writes to the same history, so one record covers them all. Each entry records the time and format the message attempt was sent. It also names the module, scheduler that produced the message, the action it was raised for, and what triggered it. The recipients and the outcome complete the entry. SecureAI records the attempts that don't reach the email server or SMS gateway, and names the reason they failed. A missing email address or an empty message is displayed in the history. Because SecureAI writes entry attempts as complete, they do not need to be synced.

    Prerequisites

    Complete the following before you rely on Notification History:

    • Enable the Notification Template permission for the technician's role so they can view notification history. Super Admin and Governance Manager roles already include it.
    • Confirm you have a working email server with Send Test Email and Send Test Messagenotifications turned on.
    • Populated attributes for recipient email addresses and mobile numbers to ensure the notifications have somewhere to go.
    • Create or enable the notification templates for the events you want a record of. An event with no notification template produces no notification entry.
    Note:
    • An entry exists only when SecureAI attempted a notification. An event that does not match an enabled notification template leaves no trace in the history.
    • Notification History cannot be exported.
    • Entries are removed only once you enable Notification history retention period in Retention Settings. Until then the history keeps growing and adding to the database size. After the cleanup scheduler removes an entry, you cannot recover it.

    Working with Notification History

    1. Navigate to Settings > Notification Template > Notification History.
    2. Select a time from Period. The options are Today, Yesterday, Last 7 days, Last 30 days, This Month, Last Month, and Custom Range. Last 30 days applies until you change it.
      • Custom Range takes a From and To value, each with a date and time. Click Apply.

      The listing returns one entry for each delivery attempt in that period, consisting of the following:

      Column What it shows
      Date & Time When SecureAI attempted the notification. The most recent attempt appears first, and you can reverse the order.
      Format Whether SecureAI sent the notification as an email or an SMS.
      Module The part of SecureAI the notification came from. Every module that uses notification templates appears here.
      Template/Scheduler Name The notification template or the scheduler that produced the message.
      Source The action or task the notification was raised for.
      Triggered By The technician or scheduler that prompted the notification. You can order entries by this value.
      Status
      • Success:The notification reached every expected recipient.
      • Partially successful: It reached some of the expected recipients.
      • Failed: It reached none of the expected recipients.
      Details The addressed recipients and documented reason a message did not go out.
    3. Filter the listing using Format, Module, Template/Scheduler Name, Source, Triggered By, Status, and Details to narrow it further. The filters are applied after the selected period, so one that returns blank may need a wider period.

    Tips

    • Check notification history before concluding that an approver ignored a request. SecureAI may never have sent the request.
    • A run of Failed entries spanning several notification templates usually points at the email server or the SMS gateway rather than a recipient.
    • Set the retention period against your audit obligations instead of disk usage, since Notification History can be the only evidence a stakeholder was informed.