The Message Queues screen

PolicyCenter lists each message destination in the Message Queues screen. To open this screen, click the Administration tab and then navigate in the left Sidebar to Monitoring > Message Queues. This screen contains cumulative information about message destinations.

From this screen, you can select a message destination and perform the following actions:

Suspend
Click to suspend the operation of the selected message destination.
Resume
Click to resume the operation of the selected message destination if that destination is in a state of suspension.
Restart
Click to restart the operation of a selected message destination.

You can also restart messaging by clicking Restart Messaging Engine.

If a message destination is running correctly, you do not see any accumulation of information in the columns on this screen. If there is a problem and messages begin to accumulate, you can drill down into a message destination by clicking the destination name. This action opens a Destination screen. From the Destination screen, you can see additional detail about any issues with a destination. This information can assist you in diagnosing the error. In particular, you can use the Error Message column to see the possible cause of a particular issue.

Destination screen

The Destination screen lists all failed or in-process messages for an account for all destinations. You can search for a particular account and then open the account’s detail view. From this screen, you can select one or more objects and instruct PolicyCenter to skip, retry, or re-synchronize any message that is still in process or in a failed state.

The Detailed Statistics table column headers have the following meanings.

Column header Meaning
Safe Ordering Object Name PolicyCenter groups messages for each messaging destination based on their associated primary object. (PolicyCenter processes messages associated with objects other than the primary object as non-safe-ordered messages.)
Send Time Time the PolicyCenter sent the message.
Failed A message can fail for several reasons, for example:
  • The message destination did not process the message successfully due to a processing error.
  • The message destination returns a negative acknowledge (NAK) indicating that the message delivery failed.
  • The message was part of a series of messages, one or more of which failed.
Retryable Error Waiting to attempt a retry. PolicyCenter attempted to send the message but the destination threw an exception. If the exception was retryable, PolicyCenter automatically attempts to retry the send before turning the message into a failure. PolicyCenter attempts to send an event message several times. Typically, you can configure the number of retries and the interval between them for an integration. Review documentation for the specific destination to find out how to configure it.
In Flight PolicyCenter is waiting for an acknowledgment.
Unsent The message has not been sent, for example:
  • The message is waiting on a prior message.
  • The destination is not processing messages because the destination is in a state of suspension.
  • The destination is falling behind in processing messages.
Error Message Error message returned if a message fails.

It is possible to filter the messages that show in the table by selecting a filtering characteristic from the filtering drop-down list.