โ06-14-2017 11:01 PM
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 how to update the STATE from โFAILEDโ to โCOMPLETEDโ. Per documentation, SnapLogic has not exposed the POST method to overwrite/update any of the attribute available in Monitoring API.
Any pointers to resolve this will be highly appreciated.
Best,
YV
โ06-21-2017 06:47 AM
Quoting: โโ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.โโ
Every run will generate new run id.
Thanks & Regards,
Naveen
โ06-23-2017 06:20 AM
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 ?
โ06-23-2017 08:33 AM
Yeah thatโs what weโll be doing now, earlier we thought itโll be easy if status can be manipulated by the monitoring API.