Update STATE of the pipeline
Hi all,
We’re planning to leverage publicly exposed Monitoring API to replay the failed messages (based on the State of the pipeline). The challenge we’re facing is, we’re not able to figure out ho...
Forum Discussion
Actually we’re designing a replay utility, which in case of pipeline failure (message not delivered because of connection issue, target system is down because of planned outage etc.) will pick the document data (message payload) from DB and will reply the it through the pipeline.
So far we’re not able to confirm if SnapLogic will generate a fresh runid/instance id for the pipeline execution because of replay. If it’s a new runid with pipeline status as COMPLETED, the problem is we don’t have means to either update the status of original ‘FAILED’ pipeline or update the runid to use the one for the failed one.
Hope this will help to explain the situation better.
Best,
YV
YV,
We know Snaplogic generated a new runid each time you execute the pipeline. How about you keep track of the status in the database and changed the failed pipeline status to completed ?
