Ignore error handler

the ignore error handler ignores the error and removes the bundle from the {{scenario singular lowercase}} flow the {{scenario singular lowercase}} run continues with the next bundle you can use the ignore error handler when you know that there can be incorrect data in your {{scenario singular lowercase}} and they don't have an impact on your processes the ignore error handler prevents turning off the {{scenario singular lowercase}} when there's an error and marks the {{scenario singular lowercase}} run as a success even in case of errors for example this demo {{scenario singular lowercase}} contains five modules the {{scenario singular lowercase}} is useful for tests and showing the effect of an error handler json parse json provides test data in the form of an array of three record ids iterator splits the array into individual bundles data store update a record updates the data in the data store data store update a record this module updates the data again this time the module works differently in the module mapping, there is a mapping that intentionally creates an error the mapping inserts a null value into the required key field, which always creates the bundlevalidationerror slack send a message sends a message to a private testing channel this is how the example {{scenario singular lowercase}} looks when we would run the example {{scenario singular lowercase}} , we would get the bundlevalidationerror if we added the ignore error handler to the update a record module, the ignore error handler would remove the bundle from the {{scenario singular lowercase}} flow the bundle doesn't enter the fifth ( send a message ) module the third bundle runs through the {{scenario singular lowercase}} for more information about error handling strategies check the docid 7 hehdtuu2xyys8 qurub keep your {{scenario singular lowercase}} running regardless of errors with the ignore error handler, you can remove the bundle that causes an error from the {{scenario singular lowercase}} flow and process the rest of the bundles in the {{scenario singular lowercase}} in addition, {{product name}} will keep running your {{scenario singular lowercase}} on schedule instead of disabling scheduling because of an error for example, the following {{scenario singular lowercase}} outputs an error in the update a record module to ignore the error and keep your {{scenario singular lowercase}} running regardless of errors, follow the steps right click the module that is causing the error in the menu, select add error handler select the ignore error handler save your {{scenario singular lowercase}} your {{scenario singular lowercase}} keeps running regardless of errors when an error occurs in the data store module, the ignore error handler removes the bundle from the {{scenario singular lowercase}} flow