Hello Amrith,
1. Getting the exact HTTP response from child → parent
In the child pipeline:
- After your REST snap (GET/POST/etc.), pass the full response document through to the output
- The REST snap outputs response_body, http.status, http.headers etc. — keep them all
- Make sure the child pipeline has a Pipeline Out snap (the output goes back to the parent)
In the parent pipeline:
- Use a Pipeline Execute snap to call the child
- The output of Pipeline Execute = whatever the child's Pipeline Out emits
- You now have the full HTTP response document available in the parent
2. Making the parent fail + trigger error pipeline with the child's HTTP error
Two approaches depending on your setup:
Option A — Child fails, parent inherits the failure
- In the child pipeline, after the REST snap, add a Mapper that checks http.status
- If status ≥ 400, route to a Raise Error snap with a message like "HTTP ${http.status}: ${response_body}"
- In the parent's Pipeline Execute snap → set "Continue on error" to false
- The parent will now fail with the child's error message, which flows into the parent's error pipeline
Option B — Parent catches and re-raises
- In Pipeline Execute snap, enable the error view (the red triangle output)
- Connect that to a Mapper → Raise Error snap in the parent
- The error document from Pipeline Execute contains error_message (which is whatever the child raised)
- Use $error_message to re-raise with the exact HTTP details
Pro tip for preserving the full HTTP body in the error:
In the child, before Raise Error, map your error message like:
"HTTP " + string($http.response_status_code) + " — " + string($response_body)
