Live Notifications Report

The Live Notifications Report returns all currently active notifications in the system. Note that in a multi-Company deployment, Super Administrators have access to the Total Live Notifications Report.

This report can be used to monitor system activity during periods of load. The report contains data when the system is busy creating and delivering notifications. The lifecycle of a Device notification is as follows (displayed in the Status column of the report):

CREATED > SERVICEABLE > DISPATCHING > DELIVERED or FAILED

For Voice Device notifications the lifecycle is as follows:

CREATED > SERVICEABLE > DISPATCHING > PROCESSING > DELIVERED or FAILED

Note: The final states of DELIVERED and FAILED are not displayed in the Status column of the Live Notifications Report.

For two-way network paging protocols (e.g., SNPP and WCTP), the report displays notifications created for querying the paging provider for status updates and responses. The lifecycle of these notification queries is as follows:

CREATED > QUERY_PROVIDER > DISPATCHING >DELIVERED_DEVICE or DEVICE_ READ or RESPONDED

Note: The final states of DEVICE_READ and RESPONDED are not displayed in the Status column of the Live Notifications Report for two-way paging protocol notifications.
To generate a Live Notifications Report:
  1. To specify the number of results to display on each page of the Report, select a number from the Results per page drop-down list.
  2. Click Start to generate the Report.
    1. If you are logged in as a Super Administrator, click the name of a Company to view the live notifications for that Company.
    2. The following table describes the information that appears in each column of the report:
Live Notifications Report – Columns

Column

Displays

Notification

Unique identifier for the notification.

Person Info

User to whom the notification was sent.

Device Info

Device to which the notification was sent.

Status

Current status of the notification (see table below for explanations).

Time Created

Date and time the system generated the notification.

Retries

Number of times the system has attempted to send the notification after sending the original notification.

  1. Refine or organize your Report results using the methods described in Working with Reports.
Note: Two-way pager notifications sent via SCTP and SNPP appear in the Live Notifications Report for one hour after sending. This is due to the mechanism used by these protocols to query for delivery updates and replies.

The following table explains the entries in the Status column of the Live Notifications Report:

Live Notifications Report – Status Column Entries

Status Entry

Description

CREATED

Live notification has been generated.

SUSPENDED

Notification has been suspended due to an out-of-coverage situation.

SERVICEABLE

Notification is awaiting processing by a Device Engine.

RETRY

Notification has been attempted but could not be delivered. An internal event will occur in the future to requeue this notification for delivery.

PROCESSING

Notification is being processed by a Voice Device Engine.

QUERY_PROVIDER

Similar to the SERVICEABLE, but notifications in this state are waiting for Device Engines to query a provider for delivery status (i.e., not waiting to send out a notification, as in the SERVICEABLE state).

DELIVERED_PROVIDER

Notification has been successfully delivered to a provider.

QUEUED_PROVIDER

Notification has been successfully delivered to a provider, but is currently queued at the provider awaiting delivery to a Device. (note that this status applies only to two-way paging protocols).

DELIVERED_DEVICE

Notification has been successfully delivered to a Device (note that this status applies only to two-way paging protocols).

VIEWED_DEVICE

Notification has been successfully delivered to a Device and the notification has been viewed (note that this status applies only to two-way paging protocols).

RECEIVED_RESPONSE

A response was received from the recipient of the notification.

DISPATCHING

Notification is being sent to a Device Engine. Notifications are expected to transition from this state within a configured threshold (default is 5 minutes); otherwise, they will be moved back to SERVICEABLE for requeue.