Lee D.

Hey Joël B. I was about to mention the tick box in gate snap, but Spiro beat me to it! Could the scenario you're facing be cause by one of your snaps being successful and sending to the gate first, then one of the others failing? I wonder if this makes the gate release its info back to the parent. I haven't observed anything similar myself.

Hi Niranjan, I have implemented this where I work. Like Lidiya mentioned, the public APIs are good to use here. I also use the "SnapLogic List" snaps. The list snaps create a list of project paths, which are fed as parameters into this API https://docs.snaplogic.com/public-apis/get-runtime-org.html, which allows you to get information from all project paths in your environment. Let me know if you'd like to see the implementation I have. Cheers Lee

Hi Todd K., did you get any resolution to your query? I'm not sure if its possible to get the invoking task from the runtime of the pipeline its self during a live runtime, however, I know a way to get the invoking task name using the runtime, but I believe it can only be done after the pipeline has finished executing (from my observations at least anyway, as when i try to feed pipe.ruuid, into the below API, i get a 404 response, suggesting that its not possible at runtime) you can use this public API https://docs.snaplogic.com/public-apis/get-runtime-org-ruuid.html, pass in the ruuid and the invoking task will be under "invoker_name" in the entity response. To get ruuids you can use this public API https://docs.snaplogic.com/public-apis/get-runtime-org.html, just pass in the appropriate parameters for what you need.