11-03-2023 04:19 PM
Dear Community -
Thanks for your help/support!
In this pipeline, how do I prevent In-Memory Lookup to execute when the REST Get snap fails? I see the sequence of execution is also incorrect. The snap In-Memory Lookup runs even before the REST Get snap runs. Please advise!
11-04-2023 05:09 PM
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
11-04-2023 11:07 PM
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.
11-05-2023 03:42 AM
Hi @jibin_s .. you should also include the in-memory lookup in the child pipeline if you want it this way try setting up the output from the REST as the left hand side then the streaming copied document as the right side this way if there's no matching output from REST it will not stream
11-06-2023 08:51 AM
Thanks, @alchemiz!
I have managed to restructure my pipeline by adding following components: