โ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-15-2017 06:23 AM
You can design your pipeline to make it look like completed.
โ06-15-2017 10:40 PM
Hey Pradhan,
What I understood from your response is, replay service pipeline should be designed in such a way that after its successful execution itโs state is marked as โCOMPLETEโ. If thatโs what youโre trying to say then itโll not solve my problem.
Basically, after successful replay of the failed interface pipeline, we want to update itโs status as COMPLETED so that itโs not picked up in the next run of replay service pipeline. And currently weโre not able to find any mechanism to update the state of a pipeline.
Best,
YV
โ06-20-2017 05:16 AM
We check pipeline status via API call to Snaplogic Cloud API. I do not think you can change the status of a pipeline there.
โafter successful replay of the failed interface pipeline, we want to update itโs status as COMPLETEDโ
doe this mean you are doign folloing steps?
โplease correct me if there are additional step you are expecting to be completed.
โ06-21-2017 01:56 AM
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