Pipeline Error Handling

When a major failure occurs in one of the transforms, the pipeline is notified and halts all active operations. This is fine in most cases, pipeline failures are typically handled in the parent workflow (check the create workflow page to learn about error hops in workflows). In some cases however, there are errors you’ll want to handle gracefully without halting the entire pipeline.

In these cases where you don’t want your pipeline to fail when an error occurs, Hop pipelines support error handling on transforms and hops.

When you create a hop from a transform that supports error handling to another transform, the Hop pipeline editor will ask you if you want to create a hop for the main output or for the error handling of your transform.

If you choose to create an error handling transform, the hop will be shown in red instead of the default black (or white, if you’re in dark mode).

For each transform that supports error handling, there are a number of options you can configure. Click on the transform icon to open the context dialog and selected the ‘Error handling’ icon.

In the error handling dialog, you can specify additional fields that will be added to your pipeline stream.

The available options are:

An example output when trying to cast an invalid date string to a date is shown below.