Error Handling

You can handle errors during a pipeline execution in the following ways:

Method Description
Pipelet-specific error handling Use the pipelet Error exit or a decision node to implement handling that is specific to the error condition. Use this method for business errors such as "product not found" or for technical errors, such as "product import could not acquire lock".
Pipeline-specific error handling using a subpipeline Create a subpipeline with a start node Error in the top level pipeline and implement pipeline-specific error handling. This subpipeline will be called when an unresolved error occurs in the pipeline or a calling subpipeline.
Site-specific error pipeline A site-specific error pipeline is called when an error isn't caught by the originating pipeline. This pipeline, called Error-Start, shows a site-specific general error page. A custom implementation can be provided.
X Privacy Update: We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used and to tailor advertising. By continuing to use this site you are giving us your consent to do this.