flow control between exception sub process and main flow: SAP CPI-IS

[sugata_bagchi2]

Hi Experts,

I have an iflow Where I have used the main flow to call a local process and defined the exception sub process to capture the exceptions within that local process. The exception sub process is configured to end with a end message step and before that step a content modifier is used to mark the message as failed explicitly, using the property - SAP_MarkMessageAsFailed = true.

However, I am seeing that when an exception occurs in the main flow, it  calls the local process and it goes to the exception sub process defined in that local process.
The  exception sub process works as expected - format a custom csv message, sends to an external http receiver using request reply and calls the end step. But, even after ending the message (and along with SAP_MarkMessageAsFailed = true.) it still passes the control back to main flow. And surprisingly, it does not execute the flow step immediately after the step where it failed in the main flow/process. It skips so many steps and all of a sudden picks a router step to execute. 
Is there a easy way to stop the message processing when it comes back from local process/ sub exception process?
And I am not sure why it is executing a router step which is far away from the actual failed step.

Thanks
Sugata
Please see the images attached.

[VijayKonam]

The pictures are not clear Sugata. Does your main flow have an exception handler? Also iFlow exception process does not mimic the traditional way of try/catch blocks. Ending the exception block with "End Message" and setting the flow status to true before that, may be nullifying it. Needs a detailed look into it!