Forum Discussion
6 Replies
- SpiroTaleskiValued Contributor
There are two ways that I can think of at the moment, of how you can implement the retry:
-
Handling the retry on the parent pipeline
- After pipeline execute, check the status using Router Snap. If its 1 then call the child pipeline again. If its 0 then proceed with post - processing steps.
-
Handling retry on child pipeline level:
- After the REST Call, to have a check for the status. If its 1 then self-call the child pipeline until the status comes to 1.
You can also implement a counter, where you will specify the number of retries.
Regards,
Spiro Taleski- RahulNew Contributor III
Can you please share export of both of the pipeline
-
- RahulNew Contributor III
Attached response screenshot
- j_angelevskiContributor III
Hi @Rahul,
If the
$entity.exports
will always be an array of a single object then you can check the status with the following expression:$entity.exports[0].status
orjsonPath($, "$entity.exports[*].status").toString()
. If theexports
array can have multiple objects with multiple statuses, then that depends which status you want to check.- RahulNew Contributor III
If status comes 1 for the first API hit then we need to retry until status comes 0.
Note: The status column can have two values (1 or 0). 1 indicates a report in progress and 0 indicates a report in progress.
- SpiroTaleskiValued Contributor
I am attaching only the skeleton of the pipelines. You should adjust them according your scenario:
-
Parent pipeline
Community_Parent_2021_12_30.slp (10.6 KB)
-
Child pipeline
Community_Child_2021_12_30.slp (5.6 KB)
Regards,
Spiro Taleski -