HCI: Proceed work after exception raised and handled

[cca4c]

Hello all,

I have a question regarding exception handling in a Splitter/gather Scenario.

I split a message consisting of several records and send the individual records to a cloud system in an extra SubProcess. In this SubProcess, an exception occurs for a record, which causes the entire processing to terminate, that is, the Gather Step is no longer called. However, the exception comes from the cloud system and occurs only sporadically. Is there a way to handle the exception within the exception sub process and continue processing so that the main process can run through to the end? At the moment, the behavior is such that processing stops completely after the exception.

I tried several approaches like using different end Message types or removing a property called "SAP_MarkMessageAsFailed" or removing all headers but nothing works.

So is there a way that the IFlow keeps working after an exception has raised?

Best regards!

[former_member572840]

Hi Christopher,

were you able to resolve this issue?

Currently I'm searching for same thing and got nothing.

Best regards,

Roza

[former_member198979]

@ctapisab and udo.paltzer - You can able to achieve your scenario like scenario 3 in the blog and instead of Content Modifier, use a Data Store to store error or Script to display error message in the Exception Subprocess also if you have multiple records in the main message then use general Splitter before this loop process in the Main Integration Process but make sure Stop on Exception is not selected in the Splitter with proper condition. One last thing to reorder your iflow like below -

1. It is better to decouple your Loop Local Integration Process based on your loop condition where use the Request-Reply by creating separate Local integration Process and use Exception Sub process here to catch and log.
2. Call this Local Integration Process has Request-Reply inside the Loop Local Integration by keeping the rest of the components in the Loop Local Integration Process.

so that message failure will be captured and continue to check the loop condition if this condition fails again then the above 2 steps will restart fresh message flow. These loop can be carried out based on your Loop Condition and Number of iterations set in the Loop Local Integration Process. I have done exactly similar in my iflow to avoid failure of Loop Local Integration Process and its working efficiently without any issues.

[Jingjie]

Hi, Hemachandan,

I am interested at your approach how the looping condition will be checked and the looping subprocess will continue running when the looping subprocess runs into error.

My scenario is as follows: I could like to implement a retry mechanism when the HTTP call to external system in the main process runs into timeout. This retry should happens e.g. 3 times. I build the looping module for the retry in the exception process in the main process. This looping module will call the looping subprocess which will set up the same HTTP call. However, when the timeout exception happens in the looping subprocess, the looping module will be stopped without checking the looping condition any more. Could you please explain in more detail how your approach could be applied to my scenario? or Does it fit at all?

Thanks in advance!

Jingjie