02-07-2022 04:22 AM
Hello,
I’m wondering if there is any way to trigger the error pipeline, without having to execute it with a Pipeline Execute snap. The idea is that I filter for Client or Server errors, which i’d like to handle differently based on the error code and in case of an internal server error, simply throw it to the error pipeline to log the error and create a ticket.
Does anyone have an idea of a good way of throwing the error to the error pipe without explicitly triggering it through a Pipeline Execute snap?
Best regards
Thomas
Solved! Go to Solution.
02-11-2022 09:15 AM
You could send the errors via a Mapper snap, then if you right click on the output circle you will see the option to ‘Link output to error pipeline’ - this will send the mapper output to the error pipeline configured in the pipeline settings.
02-07-2022 04:32 AM
What about setting the default behavior to send all of the errors to the error pipeline, where you can develop a logic to classify the errors based on the incoming data?
02-07-2022 04:35 AM
I have a generic error pipeline, which logs errors to a database and later picked up by a mechanism to create internal support tickets. I’d like to keep the default behavior without adding an extra pipeline. But generally, yes, i suppose that would work.
02-11-2022 09:15 AM
You could send the errors via a Mapper snap, then if you right click on the output circle you will see the option to ‘Link output to error pipeline’ - this will send the mapper output to the error pipeline configured in the pipeline settings.
02-12-2022 07:40 AM
Thank you, that’s exactly what i wanted to do. I saw this described in the documentation, but couldn’t figure out how to do this.
Best regards
Thomas