Notification Queue
Every outgoing e-mail and push notification waits in one notification queue until the Automation Server sends it. A sent message is removed from the queue. During daily cleanup, failed e-mail older than the Outgoing Notifications log's retention period is also removed; see Logs. You see and manage the queue in the Settings App and in the Admin Center. For the notification types that fill the queue, see Notifications Overview; for the mail server and sender settings, see Outgoing E-mail Settings.
Deleting a queued message also deletes its attachments, unless a record still holds them.
In the Settings App
In the Settings App, the Notifications group holds the Notification Queue page, which shows the queue status, the queued messages, and the commands for them.
Check the queue status
The Queue status group shows Running or Paused (notifications are being queued but not sent). While the queue is paused, the page also shows Paused by name at date and time. Below the status, the last connection error the sender recorded is shown in red; nothing is shown when there is none.
- To stop sending, click Pause.
- To start sending again, click Resume.
Only the button that changes the current state is enabled. Each pause or resume makes the Automation Server reload its settings.
Read the queue
The grid lists every queued e-mail and push message. Type reads E-mail or Push, Content Type reads HTML or Plain text, and Status reads Pending until a send attempt fails and Failed after that. The grid also shows From, To, CC, BCC, Initiator, and Executor, and the number and total size of the attachments. For a push message, the address columns read N/A and name the recipient person instead.
Initiator names the component that queued the message, and Executor names the feature: Workflow, Workflow. Item # id, Workflow. Notification # id, Test Mail, Self-Registration, or System Log. Some components have no initiator name: a message queued by the Import Wizard, for example, shows an empty Initiator. Except for the message sent when a registration is approved, a self-registration message queued by the Web App is marked as initiated by the Self Service Portal.
The Error Message column is not part of the default layout.
The grid refreshes itself every 10 seconds by default. Press F5 or click Refresh to read the status and the grid again at once.
Open a queued message
Select one message and click Open, or double-click it. The message opens read-only: you can inspect it but not edit it. Besides From, To, CC, BCC, the subject, and the content, it shows the message's initiator, executor, type, and the app a push is sent to. When the message has a send error, a panel shows it. HTML content is shown as a web page, other content as plain text.
Send messages now
In Alloy Navigator Cloud, the Settings App hides Send for every account except the support account; see Administering Alloy Navigator Cloud.
- Select one or more messages.
- Click Send.
- Confirm "Do you really want to send the selected notification?" or "Do you really want to send the n selected notifications?".
If a message fails, the Settings App asks "Would you like to continue sending the remaining records?". If the Settings App cannot connect to the Automation Server to send the messages, the page says "Force-sending notifications is not supported because your Settings App and the Automation Server are installed on separate computers. Please wait for automatic notification delivery." and stops.
Delete messages
- Select one or more messages.
- Click Delete and confirm.
In the Admin Center
The Admin Center's Notifications > Notification Queue page shows the queue status, the queued messages, and the commands for them.
Check the queue status
The Queue status box reads Running or Paused (notifications are being queued but not sent). While the queue is paused and the person who paused it is recorded, Paused by user at date shows who paused it and when. When the queue was paused in the Admin Center, that is the full name of the person who paused it and the server's local time. A stored connection error is shown as a warning.
- To stop sending, click Pause.
- To start sending again, click Resume.
Read the queue
The table's columns are Type (a link that opens the message), Queue Date, Executor, Initiator, Host, To, Subject, Status, and an attachment icon. The table is sorted by Queue Date, newest first. A click selects only that row, and a double-click opens it.
The page lists at most 1000 queued messages. This is a limit of the list, not of the queue: when the queue holds more, the page lists 1000 of them, chosen in no reliable order, and the messages that are not listed stay in the queue. The sorting by Queue Date applies only to the listed messages.
Open a queued message
Double-click a message, or click the link in its Type column. The Notification drawer opens read-only, with a Close button. It shows Type, Initiator, Executor, From, To, CC, BCC, and Subject. An empty From reads "System defaults (address)", the installation's default sender. A plain-text body is shown as text and an HTML body as a page; the notification style sheet is not applied to it, and its links open in a new browser tab. A body of any other content type, or an empty body, is not shown. A stored send error is shown in a red Error Message box.
Send messages now
In Alloy Navigator Cloud, the Admin Center does not offer Send, and the server refuses a send request; see Administering Alloy Navigator Cloud.
- Select one or more messages.
- Click Send.
- Confirm "Do you really want to send the selected notification?" or "Do you really want to send the n selected notifications?".
The messages are sent one by one. If one fails with an error message that is not marked as confirmed, sending stops and the error is shown; the failed message is not sent again. A failure that carries no error message does not stop the sending. When messages remain, the Admin Center asks "Would you like to continue sending the remaining records?". No message confirms a successful send.
Delete messages
- Select one or more messages.
- Click Delete and confirm. For more than one message, the confirmation states the count.
The selected messages are deleted together. If any of them cannot be deleted, none of that request's deletions take effect, and the Admin Center shows the errors one at a time with Skip and Cancel, or only Ok when it is the last error and nothing is left to send. When the next error repeats the same message, the choices are Yes, Yes to all, and No. After you go through the errors, the messages that had no error are deleted in one follow-up request. When more than one message was selected and the last request contains at least one message, a result message reports a count: the number of messages sent for deletion in that last request, not a count the server confirmed.
Set the check interval
The notification queue check interval is on the Notifications > Global Settings page. In Alloy Navigator Cloud its minimum is 60 seconds, and a lower value is raised to 60 seconds when it is saved; see Administering Alloy Navigator Cloud.
How the queue is sent
While the Automation Server is active, it checks the queue at the queue check interval. It also checks the queue once when it becomes active, such as when the service starts. At each timed check it starts one sending pass for each message type, e-mail and push. While sending is paused, no pass sends or fails any message (see Pause and resume sending).
- Check interval. The queue check interval is 10 seconds by default. On premises, the smallest value the Settings App accepts is 1 second. In Alloy Navigator Cloud, the Automation Server and the Settings App use 60 seconds when no value is stored, and the Settings App does not accept a value below 60 seconds. In the Admin Center, the Cloud minimum is 60 seconds, and a lower value is raised to 60 seconds when it is saved (see Administering Alloy Navigator Cloud). To change the interval, see Outgoing E-mail Settings.
- Order. Messages that have never failed are sent first, in order of their queue date. Messages that failed before are tried again after them, so a message that keeps failing does not hold up newer ones. When only failed messages of one type (e-mail or push) are left, the regular checks leave the messages of that type alone until the Automation Server next becomes active or someone sends them manually.
- Test messages. The automatic sending holds a test e-mail message back for at least 30 seconds after it is queued, so that it is not sent with the mail settings the Automation Server still held when the message was queued.
- Success. A sent message is deleted from the queue. A delivered push notification is first copied to the history of delivered pushes; a delivered e-mail is not kept. A push notification whose recipient has no device registered for the app it targets also counts as sent and leaves the queue, although it reaches no one.
- Failure. A message that fails stays in the queue with the error text and the time of the attempt. For messages that are not system messages, the failure is also recorded in the system log. A message without a recipient is marked failed unless the installation is set to delete such messages; that option is off by default.
Pause and resume sending
Sending is allowed by default. Pausing the queue stops the automatic sending of queued messages without changing any message. New messages keep collecting in the queue while it is paused. A message you send with Send in the Settings App still goes out while the queue is paused. Pausing records who paused the queue and when.