Continue the process despite having an error in an OData call

[Xavi]

Hello everyone,

I would like to know how to make a process not stop even if the OData response is wrong (it is not a Batch process).

The case that is we have 2 independent processes that can be executed at the same time which can sometimes update the same BP.
If this happens one of the two ends up in an error because the other has the BP blocked, I get a 400 error but I can't handle that error in any way.

I would like if I receive a 400 error to finish the message correctly without error and and go to the next step, If it is another type of error, it does have to end in error.

The problem is that the OData adapter ends the message or executes the exception whenever there is an error, and it does not let those errors be handled in the process.
In the exception process, you cannot put a condition to end in one way or another, you can only contain a type of ending.

It is an unusual case but necessary for the business process.

Does anyone know how to solve this need?

Thank you in Advance,
Javi

[VijayKonam · Accepted solution]

Ttypical situation. One way of handling this was to break the iflow into sub-processes or even separate integration processes. The subprocess would catch 400 in an exception branch and ends it in no error. So that the caller process can continue later on. However, if you have to continue from that point, you may have to break the iFlow in separate integration processes and make the exception handler call the next process via process direct by providing the current context (payload, properties and headers).

[Xavi · Accepted solution]

Thank you for the response Vijay.

Kind Regards,
Javi

[Zupa]

Another solution is to replace the ODATA call with HTTP.
Then remove the flag from the "Throw Exception On Failure".