Prevent further execution if an error occurred in a snap

Hi jibin_s ,

Good day, had a similar scenario before...as a resolution I decoupled the pipeline then in the child pipeline set the all snaps "when error occurs" to "Stop Pipeline Execution" in this way any error that will occur in that child pipeline all on-going process will be aborted thus failing the pipeline then error will bubble-up to the parent pipeline from the pipeline execute ( if possible the child pipeline is reusable ) you can then trap/log the error

The refactored pipeline will be looking something like this ... 
Parent/Main pipeline

Child Pipeline (2)

EmEm

jibin_s - The reason that the In-Memory Lookup is being called is because you have "handled" the error from the Pipeline Execute by opening the error view on that snap, so the output view successfully closes and the In-Memory Lookup snap gets no data in the 121 bottom path (empty result) and still has the data from the 117 path, which is a perfectly valid state.  Because SnapLogic is a streaming platform, I believe the In-Memory Lookup and all subsequent snaps in that path are simply finishing before the Exit snap has a chance to fail out the pipeline.

Thanks, alchemiz!

I tried the solution but unfortunately it did not help me. Following is the screenshot of the execution. In it you could see that the Pipeline Execute is failed but still the In Memory Lookup executed successfully. 

jibin_s - If you move the highlighted snaps into a child pipeline and check the success of the return, it will prevent the downstream from executing.