Skip to Content

HCI: Proceed work after exception raised and handled

Mar 23 at 11:09 AM


avatar image

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!

10 |10000 characters needed characters left characters exceeded
Former Member

Hi Christopher,

were you able to resolve this issue?

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

Best regards,


* Please Login or Register to Answer, Follow or Comment.

1 Answer

Sriprasad Shivaram Bhat
Mar 23 at 01:24 PM

Hello Chris,

Click on Splitter and uncheck the Stop On Exception.


Sriprasad Shivaram Bhat

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Sriprasad Shivaram Bhat,

thank you for your answer, I already checked that option, but this checkbox handles the exception processing within the splitting branches. So with your solution, the process runs to the gather step and stops there. I need a way to make the IFlow run to the designed end after the gather step.




We are also stuck on the same issue. Were you able to figure it out?