I am calling a data flow in a process flow. The data flow calls a strategy. I have simulated a divide by zero exception in the strategy. When I ran the tracer I noticed that the error gets suppressed by the pzRunDecisionDataFlow. Is there a way to catch this error when the data flow ends and the control gets back to the process flow?
The tracer output is attached. The step status fail vanishes after the activity pzRunDecisionDataFlow ends.
***Edited by Moderator: Lochan to update platform capability tags***
The error is propagated as an exception to pzRunDecisionDataFlow activity. We should catch this exception and add an error message to the work page like I made a quick change in the system you have provided.
But I am not sure if it is required to send the errors back to case during run time as the DF results no offers if there are issues and this shape is not part of any assignment/flow action/harness() instead it’s an advanced shape like an utility shape.