Hi SL gurus,
I designed an async pipeline, see picture.
I created an error pipeline and defined it in my async pipeline properties.
I created a triggered task for my async pipeline.
Now, to simulate an error, I put some trash into JSON Formatter.
Whenever calling this erro pipeline, the error pipeline gets ‘STOPPED’ and throws an error:
“Mapper[5da81a2d878b923ec79c3a7d_473187f9-8ccf-4d12-960b-2c5bdfcb71a2 – 17c15874-2051-4a28-9e3f-c265f73416ce]
com.snaplogic.cc.snap.common.ThreadDetails: prio=4 Id=6469533 WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@14f2b639
at firstname.lastname@example.org/jdk.internal.misc.Unsafe.park(Native Method)
- waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@14f2b639
If i execute the pipeline directly with some mapper in front of it, it fails and error pipeline fails with:
"Reason: The root pipeline execution is no longer running"
This error is telling me NOTHING.
I would expect the error pipeline to write a JSON file, as designed, not to fail.
Any hints are more than welcome.
So what is the proper design of error behaviour, so I do not get trash like this?
Yes, I went through this already: