Message reprocessing

When BODs are delivered to your application inbox/outbox tables, it is the application’s responsibility to consume or reject them due to circumstances. There are options to set intervals in ION Desk to clean up inbox/outbox tables. You can develop your own clean up scheme considering BODs volume and storage.

In case of processing inbound BODs fails for business data integrity, we recommend that you develop a user-driven retry mechanism. For example, workflow integration rather than mandating business users to submit the document for approval again. For technical reasons, it makes better sense if the system admin is able to resubmit the same BOD to get through. Same with consuming transaction BODs, ledger entry or purchase order quite often a retry is mandatory to sort out interdependency of BODs delivery.

When developing system automatic retry, it is important to retry at reasonable intervals and end the process if the problem is not solved. This is to avoid deadlock of your integration engine focusing on a few BODs and leaving the Inbound BODs queue too long to process.