Reprocessing and redelivering messages

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

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

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

The system automatically attempts to reprocess qualified messages based on the following incremental schedule:

  • The system attempts to reprocess after 5 minutes
  • The system makes a second attempt to reprocess 10 minutes after the first attempt
  • The system makes a third attempt to reprocess 60 minutes after the second attempt
  • The system makes a fourth attempt to reprocess 5 hours after the third attempt
  • The system makes a fifth attempt 24 hours after the fourth attempt
  • After the fifth attempt to reprocess the record, the system will make no further automatic attempts to reprocess the record, which is indicated if Next Scheduled Retry is empty. However, you can manually attempt to reprocess records as necessary. See Reprocessing and redelivering messages.
    Note: 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.