SAP CPI. Exception Subprocess not being triggered in iflow

[mikereybal31]

Hi Experts,

I am having the following issue with one iflow.

Context. I have two iflows that they have almost the same process, the go and extract infor from Successfactors and they send it to a third party system. The issue is in the part of the messages when they both fail. First iflow is doing this correctly, if it fails, the exception subprocess is triggered and it sends the email to the recipients correctly. The second iflow with the same similar logic in a local process is not triggering the exception subprocess when it fails.

Please see attached both scenarios.

Working good iflow.

Not working iflow.

The error is not the important issue here. In this case the issue is "HTTP Request failed with error : Connection reset, cause: java.net.SocketException: Connection reset" but it happens with all the errors, for the first iflow whatever error is happening, it is always triggering the exception and sending the emails. And for the second one is not working and not event going to the exception subprocess at all.

Please let me know if you have had encounter this issue or if you know if something might be missing in the iflow with the failure?

Many thanks, I appreciate your help.

[YayatiEkbote]

Hello Miguel,

I see that your IFlow has sequential multicast. We also faced similar issue in our iflow and we raised issue to SAP. We came to know that sequential multicast has a limitation.

3028577 - Exception Subprocess in SAP Cloud Integration does not execute in case of error on nested multicast branches

Regards,

Yayati

[mikereybal31]

Thanks for your response Yayati.

The iflow was built in the way that each one of the sequiencial multicast are not in the same local process as the note indicates.

After making some tests I figure it out that the issue was because the iflow had older version of the objects, let me explain, this iflow was created long time ago and I just tried by re-creating again the SF Query local process call and it worked. It seems that probably there was a versioning issue at object level that was not allowing to pick up any of the errors happening at the local process. This was weird but re-creating again solved my issue.

I appreciate you help.