Hello everyone,
We are currently trying to improve our pipelines by adding error paths and are having problems with the JMS Consumer snap.
Unlike other snaps, like the SQL Server snaps, where a connection failure is routed to the error path, a connection error on our JMS snap does not trigger the error path and fails (see attached image).
Is there a way for us to catch those errors without ending with a failure ?
Please note we do not use ultra pipeline/ultra tasks, but a regular schedule task to run this pipeline.
Edit for clarity :
Error is not triggering error path
Here same type of error (connexion error) is triggering error path (don’t mine the failure on the next box it was expected here)
1 ACCEPTED SOLUTION
@Lydia If you want to explicitly stop your pipeline after send some action (logging/notifying) you can use EXIT snap and config till how many no of document it accept like 1 in below pic. You can also customized you error message on exit error message filed. If you config that pipeline as task and select notification in case of failure, people will get snaplogic platform generated mail with your custom error message.
Hi @darshthakkar, thanks for the comeback !
The snap works just fine usually, I was currently trying to trigger an error by using the wrong password to see if the error path was working correctly, because error caused on MQ issues needed to be foward to a different team than the team managing the rest of the pipeline in production.
My issue is not the error itself but the fact that it doesnt go to the error path and instead fails right there.
In comparaison when i use the wrong SQL password on the SQL snap it triggers the error path correctly :
(dont mind the fail on the error box itself cause it’s using the same sql account 😅 )
