Automatic Shutdown of Blocked Recipient After Two Weeks

Note: This update represents only a portion of the AMS360 24R2 release. Please navigate to AMS360 2024 R2 Release Notes to review other enhancements and fixes that were part of this release.

With previous releases, if a notification recipient was misconfigured or not responding, notifications sent to that recipient were deleted whenever a new notification arrived for that recipient. Also, notifications are only attempted to be sent once. Broken recipients can be detected via the Undelivered Notification Messages screen, but in the past they needed to be manually cleared and shut off by an AMS administrator.

With this release, if a notification recipient is misconfigured or not responding, clearing it will not require customer intervention.

  • If the notification recipient is set to Single Retry, it will try each notification twice and then delete the notification. Follow-on notifications will continue to attempt to be sent to the recipient. If the notifications are misconfigured, they will continue to be sent and will fail (because of the misconfiguration).

  • If the notification recipient is set to Blocking, all notifications for that recipient will remain in the queue, and the oldest will be resent to the recipient up to nine times over the course of two weeks. If the recipient has not accepted the notification within that two-weekperiod, that recipient will be automatically turned off. This will delete all pending notifications for that recipient. The administrator will see a message when logging into AMS360, warning of any recipients that are not accepting notifications.

Notification recipients set to Single Retry:

  • If the notification recipient is not working, notifications will be deleted after two failures.

  • When the notification recipient is brought online, new notifications will work automatically, starting with notifications created after the recipient was brought online.

Notification recipients set to Blocking:

  • A notification recipient is set up with a bad URI or whose recipient is not working.

  • The administrator is notified upon login that some of their notification recipients are not being sent.

  • The administrator can either manually correct the configuration or inform the notification recipient owner of the issue.

  • Once the issue has been fixed, the administrator can either delete the old notifications or resend them.

  • If the administrator chooses to ignore the issue, any notifications set to "blocking" that are not responding will be shut off after two weeks of not accepting notifications. Notification recipients set to "retry once" will continue to have them sent, unless the configuration is manually changed; nonetheless, in this case, all failed notifications will be automatically deleted.