Allow retries for the notification dispatcher

Occasionally when a notification trigger is defined using a Before Insert, the system is unable to identify the object immediately and the notification fails. Using this new profile option, in the event that there is a notification failure, a number of retries can be defined. This will improve the reliability of the notification framework.

Currently, after dequeuing an event, the notification dispatcher thread attempts to enrich the event with all the details of the business object record. However, in scenarios with extensive customizations and triggers, this process may occur before the record is created, causing a delay in record persistence. As a result, when the notification dispatcher tries to query the record before it has been persisted, a "record not found" exception may occur. This profile option enables the system to retry building the dispatch event, preventing this issue from happening.

Steps to Enable

There are two profile options which can be used to address this issue:

ORA_SVC_NOTIFICATION_RETRY_COUNT

• Retry Count for Sending Unprocessed Notifications

• Default value is 3.  This profile option provides a list of values which you can select for the number of retries

ORA_SVC_NOTIFICATION_RETRY_DELAY

• The delay in seconds before unprocessed notifications are retried.

• Default value is 0. This profile option provides a list of values which you can select for the number of seconds.

To set a profile option, use the following steps:

• Login as a user with Administrator privileges
• Navigate to Setup and Configuration
• Search for Manage Administrator Profile Values
• Search for the profile option name
• Select the desired value