Forum Discussion
Hello adityamohanty,
You could with the following approach:
- Generate a document per page. (Dynamically based on the page count and page size from the initial response)
sl.range(1,$page_count+1,1).map(x => {"page":x, "page_size":$page_size})
- Split the array using JSON Splitter Snap.
- REST GET request per each document.
I chose this approach since I'm not aware of the format of the response of the models endpoint. If there are pagination information, you could achieve the same using REST GET Snap or HTTP Client Snaps with proper pagination enabled.
You can refer to the pipeline attached below and let me know if this helps you.
Regards,
Aleksandar.
Hi,
I have tested a bit more. If I force an error in e.g. Mapper3 or LogMessage (see picture below), I see the child-error-pipeline getting executed fine. Only, when I force an error in JSON Formatter Snap, it fails with the error message mentioned in the initial post.
Is it a BUG or a FEATURE, that JSON Formatter does not call error pipeline properly? Are there other snaps with this FEATURE?I also noticed, that the child-error-pipeline only gets executed once, for all the errors in the pipeline, WOW-1!
What is more, even if errors occured in more snaps, pipeline gets executed further, and I see “Completed” status in the Dashboard, WOW-2! ← this probably is why, error pipeline gets executed only once. Is there a possibility to force the pipeline to stop on error and use error pipeline?cheers
Simon 🙂