Forum Discussion
Hi @pjanapati and welcome to the SnapLogic Community! 🙂
If the snaps that you are using does not support Pass Through, then you can add Copy Snap and a Gate Snap after the Salesforce Snap.
That way the Gate Snap will wait until it collects all of the documents, in this case until Salesforce Snap completes.
Afterwards just split the documents coming directly from the Copy Snap.
Skeleton Flow:
Sample Pipeline:
SL-Comm-Sequentially_2023_02_28.slp (8.8 KB)
Also, you can achieve the same with many different approaches like: pipeline nesting and pipeline execute, copy and join snap etc.
Let me know if this helps you.
BR,
Aleksandar.
Hi Aleksandar,
Can you provide some more information on the other approaches you mentioned to ensure the pipeline runs sequentially? I am looking to call some other pipelines from a single pipeline and want to make sure that everything downstream waits until the Pipeline Execute snap finishes completely. Thanks.
- PSAmmirata5 years agoEmployee
@ptaylor - Once this change is implemented, is the Exit snap the best way to programmatically stop the pipeline once the Head’s output view is closed?
Why do you need the pipeline to stop if the output file containing the analysis results has been written and closed?
But, yes, I suppose you could add an Exit snap after the File Writer if you do want the pipeline to exit. But even if you don’t, the File Writer will have completed and written the file that your user needs, even while the Head continues to consume its input and the pipeline continues to run.
- PSAmmirata5 years agoEmployee
If we no longer need the pipeline running, I don’t want to use Snaplex node resources unnecessarily. Also, users question why is the pipeline still running once it produced the desired file.
Related Content
- 3 years ago
- 4 years ago
- 6 months ago