Recursive logic in Snaplogic
The pipeline was failing in production because it was calling the child pipeline for more than 64 times.
Do we have any workaround for this approach
Forum Discussion
@sravankunadi - to make pagination a bit easier, I recommend that you build the complete URL, including the query parameters (except “offset”) in a Mapper just before the REST Get. This might take just a bit of testing to work out the correct syntax of the “root” element.
Then the REST Get properties could be set as follows:
- Has Next: $entity.result.length == 200
- Next URL: $original.url + “&offset=” + parseInt($entity.result.length) -1
Unfortunately, if the API doesn’t return a “next url”, you will need to build the full URL for the Next URL value.
Since I can’t call your service, I’m not able to replicate the folder pagination; and because I don’t have a Marketo instance with a large number of folders, I can’t provide a sample pipeline for you.
Hope this helps point you towards a solution!
