This tutorial explains the user what message reprocessing is and why we need this functionality. It describes the manual reprocessing and the automatic reprocessing done by the "MessageReprocess" job. It also explains which status make sense to be reprocessed and which not.
MessageReprocess Job is the process to be used for reprocess failed and pending message from the previous integration. It might be failed if the user does not edit or edit wrong business logic in IMessage Data.
Following, we will show you how to use MessageReprocess job to correct the message records in different cases. The different cases we support are:
– Pending Message (Yellow)
– Failed Message (Red)
Message is Pending becasue of a lot of reasons. They have been shown in Comment. It is one of many reasons that casues Pending, as an example below “This message is not met a condition of all workflows.“
Note: You must correct your data to meet the condition of all workflows first before you can reprocess.
– Manual Reprocess
After you correct your data and ready for reprocess, please selects on which messages you want to reprocess then click on button Reprocess.
– Schedule MessageReprocess Job
Navigates to Integration Admin -> Scheduler -> MessageReprocess
- Finds which Integration name you would like to use schedule
- Sets how many minutes you would like schedule to run
After that, Next Schedule Run will be appeared as in the picture mentioned below. You will be able to see the actual time that schedule is going to run “5.24AM“.
Note: Pending Message sometimes might have become Failed because of missing some field.
Message is Failed because of a lot of reasons, they have been shown in the Comment. This is one of many reasons, such as it missed some fields and incompleted. As you can see the screen shot below, it is “After evaluating the data source (accountname), no data passed for the mapped external id field (Name) and After evaluating the data source (accountname), no data passed for the mapped external id field (Name).“