Thanks tlikarish, my use case is a end user facing Job Management interface embeded within our ERP solution. I want to allow users to retry whole or in most cases just parts of pipelines in the event of errors and I wanted to do so without needing to manually capture additional info for every pipeline - hence wanting to base the soution around the Ruuid and the associated info available to me from the SnapLogic Public API’s.
I have briefly looked at resumable pipelines thankyou, but in addition to the need for a subscription, unavailability of an endpoint is just one potential use case. More commonly its related to data quality issues, we want to allow users to resolve and then recover any related failed integration messages (or more cruicially just failed parts without rerunning the whole).
I’ve gone down the route of checking for and if not found creating what is a throwaway triggered Task in a dedicated project that I can then call, pass parameters (and as a bonus if needed a payload) to via a REST GET/POST. I think this (along with the info I am capturing in my own logs) will give me the technical flexibility to retry any failed pipelines (parent or child) without having to specifically configure/build them to allow me to do so.
Its borderline ellegant… or at least I hope has the potential to be so.
