Fault handling in nested shared flow

Not applicable

Is there way to handle faults thrown by a shared flow in another shared flow without doing two shared flow calls from proxy?

I have the following scenario:

6674-apigee-flow.png

1) proxy A calls shared flow A
2) shared flow A executes policies X and Y
3) shared flow A calls shared flow SB(owned by some other team)
4) shared flow B executes few policies and in some cases raises a fault

Is there a way to handle the fault raised by shared flow B in shared flow A without adding one more shared flow?

0 1 511
1 REPLY 1

You could encapsulate and handle faults by using a chained proxy.

There's no equivalent to a "catch". You cannot catch faults in SF B, within SF A.