Resume error handler

the resume error handler replaces the module output with a substitute output when an error happens you define the substitute output in the resume error handler settings the rest of the {{scenario singular lowercase}} uses the substitute output {{product name}} processes the rest of the bundles in the {{scenario singular lowercase}} flow normally 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 resume error handler to the update a record module, the resume error handler would replace the bundle with the substitute mapping when the module outputs an error, {{product name}} would use the substitute bundle instead the third bundle runs through the {{scenario singular lowercase}} you can use the resume error handler when you have a substitute mapping that fixes the bundle and allows the data bundle to continue in the {{scenario singular lowercase}} flow you can also use the resume error handler to add a placeholder that marks the data bundle to check later for more information about error handling strategies check the overview of error handling docid 7 hehdtuu2xyys8 qurub change the bundle when it causes an error with the resume error handler, you can substitute the bundle that causes an error with your custom data the custom data continue the rest of the {{scenario singular lowercase}} flow instead of the erroring bundle in the resume error handler settings, you get the same fields as in the handled module settings in the error handler fields, you can provide custom data that {{product name}} uses instead of the bundle that caused the error for example, the following {{scenario singular lowercase}} outputs an error in the update a record module to change the erroring bundle for custom data and use them in the rest of the {{scenario singular lowercase}} , follow the steps right click the module that is causing the error in the menu, select add error handler select the resume error handler fill in the resume handler settings with your custom mapping save your {{scenario singular lowercase}} you added the resume error handler to your {{scenario singular lowercase}} when an error occurs in the data store module, the resume error handler replaces the bundle with your custom mapping