cancel
Showing results for 
Search instead for 
Did you mean: 

To fetch the failed records of the previous run in the current message run

0 Kudos

Hi Experts,

Currently in couple of our integrations, we are fetching student registrations in delta data form based on last successful run.

But, If there is any failure of the student record at mapping, the entire data is not flowing to the target system.

Our requirement, is the iflow should not stop on failure and continue processing the correct records to target system and most importantly the failed record should be available or to be fetched in the next run and continue processing with the new records. I am using odata v2 adapter.

Is there any way to acheive this ?

Note : We have not configured any interating splitter to uncheck the stop on exception feture based on requirement.

Hope the above information clarifies. Please let me know if you need further information on this.

Regards,

Amuktha

Accepted Solutions (1)

Accepted Solutions (1)

Sriprasadsbhat
Active Contributor
0 Kudos

Hello Amukta,

Better way to achieve this is to handle all foreseen error scenarios ( as you have mentioned mapping failure you can handle this and mark this record for failure with extra field like error ) in your iflow.

Once you are done with processing you can store this record in DataStore for future reference. Everytime you run the interface have a branch to check if previous run error exist or not( Put Select step to pull the data ).If it exist then try to fix or take necessary action as per your requirement and then merge the corrected payload with your original payload & proceed with your further processing.

Regards,

Sriprasad Shivaram Bhat

Answers (0)