Error pipeline failing
I built an error pipeline. It works perfectly with some of the pipelines i built, but with others it won’t work. Seems like no error information is being passed to the error pipeline. What am i getti...
Forum Discussion
@rmedeiros Looks like it’s syntax issue (count not found). In your error pipeline you don’t need to explicitly map each and every attribute. Rather have one open/unlinked input view mapper and use pass through option. Just add one/two fields in mapper (name of error pipeline name/ execution time etc.) and use the pass through.
If you don’t want to change your logic then select null safe option in your mapper in error pipeline.
Well, i tried turning on the Null Safe and Pass Through options. But some pipelines kept throwing this error on the Error Pipeline. Despite throwing this error, the error pipeline is kind of working, it saves an error log and creates a ticket, as intended, but the error log is an empty JSON, with only the empty brackets. Seems like no error info is being sent to the error pipeline.
@rmedeiros Is it possible to share your error pipeline ? you can remove your endpoint details before sharing.
errorSimulator_2022_06_01.slp (6.3 KB)
errorReporting2_2022_06_01.slp (15.8 KB)Ok. This is the Error Pipeline. It works perfectly when i trigger it from this errorSimulator pipeline.
When an error from other pipeline triggers it, it throws the following error but still saves an log, creates the ticket and the branch, all with an empty error json: ."Error pipeline failed
Reason: [{ruuid=f5c2ab51-9f58-4942-b8de-4e21a0a4399e, label=ErrorLog Mapper, failure=Unable to write to JSON-Path: $.snap_details.views.out.output0.count, reason=Expecting object for JSON-Path field reference ‘count’, found: null, resolution=Change the path to refer to an object}]
Resolution: Fix the errors reported in the error pipeline"
@rmedeiros sorry for late response. You can refer attached pipeline.
errorReporting2_2022_06_03.slp (14.2 KB)
