@chmurray88 I am not sure if I am getting your question correctly or not but If your pipeline get executed, it should have runtime id. I believe your third party scheduler call your pipeline by trigger task. If so, you can use a mapper (with runtime id)after completion of your business logic as success response flow (A) and for error scenario also you can union all error scenario and add fail mapper explicitly with runtime id(B) and then union A and B in your pipeline.
You can refer a simple pipeline attached here, this pipeline expect json data, if you pass json body it will give you runtime with success message else give you runtime id with error message.
responseFromErrorPipeline_15_2021_06_04.slp (6.3 KB)
