Skip to main content

Errors and Retries Guide

Retries and How They Work​

When the Smart Alerts system does not receive a response for an alert event, it is assumed that there was a transmission or connection error. Smart Alerts has automated functionality that will attempt to resend the alert event. In order to use this functionality, your system must be able to filter duplicate alerts (see below). The max retry amount is configurable up to 3 retries. Message retries will not be triggered if a response is received from you, even if it is an error response.

If you decide not to have the auto retry function enabled, it will be up to the Financial Institution to review failed alerts within EZAdmin on the Smart Alerts Exceptions screen and manually re-send the alert (see the document "Smart Alerts Exceptions Monitor User Guide" located on the downloads page for more details) or potentially handle outside of the Ensenta system.

Duplicate alerts​

In order to leverage the automated retries, your system will need to have the ability to filter out duplicate alert messages. This ensures that no alert is actioned twice (in the event that an alert was received by your system, but Ensenta did not get a response from you).

You will need to utilize the ECAlertLogId to identify duplicate messages. This data element is a unique identifier for the alert message, each alert message will have a unique ECAlertLogId unless it is a duplicate of a previously generated message. If your system recieves a message with an ECAlertLogId that is a duplicate of a previously received message, your system should then handle the message appropriately so it does not get actioned a second time, then send a success response back so that we do not continue sending further retries.

Error Handling​

The following scenarios are considered exceptions:

  • No response is received (will trigger a retry)
  • An error response code (any response code other than “00”) is sent in the response (will not trigger a retry)

The Financial Institution is responsible for reviewing and ensuring all exceptions are handled and processed appropriately since Ensenta will not automatically send message retries when we recieve a response from you.

Jack Henry/Ensenta provides two methods for Financial Institutions to identify/review attempted alert events:

  • The EZAdmin Alert Log screen logs all alerts (successful and unsuccessful) for research purposes. This screen allows you to see details for each alert, as well as resend alerts. See the document "Alert Log User Guide - External" on the downloads page for details.
  • Ensenta has an endpoint down notification service that runs every 15 minutes and will look for any unresolved exceptions from the last fifteen minutes. It will then send an email to the address specified during the Alert Route setup process if it detects a high number of exceptions. See the document "Smart Alerts Exceptions Monitor User Guide - External" on the downloads page for details.