1.5 Notification Retry

This topic describes about the notification entry.

The notification retry feature enables automatic processing of failed notification records without needing user intervention. Failures in notification can occur due to SSL handshake or temporary connection issues, leading to records being unprocessed and marked as ‘E’. This feature ensures that these failed records can be retried according to the configured retry criteria once the root issue is resolved.

A new feature called NOTIF_RETRY is maintained through the Feature Maintenance (CSDFTRMN) screen to retry notification messages. It is enabled for the Head Office branch through the Feature ID Maintenance (CSDFEMNT) screen. After enabled, the PL/SQL scheduler job can be configured using the Job Maintenance (STDJOBMT) screen. This job runs on a Quartz scheduler at a configurable interval.

Note:

The shorter interval duration will not help for retries in case of connection failures. The recommended interval is every 2 hours; however, the bank can adjust the interval as required.

The retry job can be executed only if the NOTIF_RETRY feature is installed. On each execution, the job checks the current retry count against the configured maximum count:

• If the retry count has not reached the maximum, the count is incremented and the status is updated from ‘E’ (Error) to ‘U’ (Unprocessed).
• If the retry count has reached the maximum, the status remains ‘E’ and no further retries are attempted.

The existing Notification job remains unchanged and continues with the status as ‘E’. When the retry job resets the records to ‘U’, they are automatically picked up and processed again. The user can stop or resume the jobs using Job Details screen (SMSJBBRW).