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.
