Reprocessing and redelivering messages - HxGN EAM - 12.0 - Administration & Configuration

HxGN EAM Databridge System Administrator Guide

Language
English
Product
HxGN EAM
Search by Category
Administration & Configuration
HxGN EAM Version
12

Reprocess transactions to re-route a document if Databridge does not process a transaction successfully.

Automatic attempts to reprocess a message are made if the Processing Status of the message is F (Failed) or PF (Partially failed) and if it is determined that the type of processing error requires it to be reprocessed. A record needs to be reprocessed if the processing failed due to a system/environment error or a business logic error. F processing status is assigned if all parts of the message fail. PF status is assigned to a message for which some parts of the processing failed, but not all.

Automatic attempts to re-deliver a message for request processing and response delivery are made, regardless of the current delivery status. However, a message is only qualified for re-delivery if the Delivery Status is F and if it is determined that the message needs to be re-delivered. It is determined that a record needs to be re-delivered if the delivery failed due to a system/environment error or a business logic error. TN status is assigned if a message has been successfully delivered to the trading network but has not yet completed the delivery cycle. TN status is only assigned to messages in a hosted Databridge installation (using Infor's ASP services).

Automatic attempts to reprocess qualified messages are made based on the following incremental schedule:

  • An attempt to reprocess is made after 5 minutes

  • A second attempt to reprocess is made 10 minutes after the first attempt

  • A third attempt to reprocess is made 60 minutes after the second attempt

  • A fourth attempt to reprocess is made 5 hours after the third attempt

  • A fifth attempt to reprocess is made 24 hours after the fourth attempt

  • After the fifth attempt to reprocess the record, no further automatic attempts to reprocess the record are made, which is indicated if Next Scheduled Retry is empty. However, you can manually attempt to reprocess records as necessary. See Reprocessing and redelivering messages manually.

    Next Scheduled Retry is based on the Processing Retry Schedule defined for the Databridge partner on the Partners form. See Configuring Databridge partners, Setting up partner processing retry schedules, and Setting up partner subscriptions.