Forum Discussion
Hi @vaidyarm,
You could try and create a triggered task for the pipeline you want to execute on a different snaplex from the first one. In the Task’s settings you can specify the snaplex on which you want the task to execute.
Then, you may call the triggered task by using a REST Post Snap. I did a little test, and successfully passed 9,53 MB of data to the pipeline in the triggered task, by using a REST Post Snap.
Let me know if I can help you further. If you want I can share some pipelines that can illustrate this solution.
BR,
Dimitri
Thanks @dimitri.hristovski for this design proposal, I will try this option.
Could the REST Post done can be tied to same execution ? (like we see child pipeline tied to its parent visible from dashboard). i am looking at this from auditing perspective, as in case when we search for any particular transaction status if any error occurred, it should pop up on searching dashboard.