In a CPI iFlow I am connecting to a receiver via the OData adapter and am getting the below response:
com.sap.gateway.core.ip.component.odata.exception.OsciException: : 202 : HTTP/1.1
I believe 202 is not really an "error" but is causing the iFlow to fail. Currently I am utilizing an exception sub process to handle the remaining steps, which is working fine if there is only one record, but in case of more than one record I need to continue processing records (from splitter). Is there a way to force CPI to not treat 202 as an error and continue on with normal processing?