Break error handler

the break error handler removes the erroring bundle from the {{scenario singular lowercase}} flow {{product name}} stores the error message, mappings and the remaining {{scenario singular lowercase}} flow as an incomplete executions docid 6zznn7v35herrcjfccp9q depending on the break error handler settings, {{product name}} retries the incomplete {{scenario singular lowercase}} runs automatically or stores them until you resolve them yourself automatic retry is most effective for temporary errors or errors where another attempt might be successful {{product name}} automatically retries the most frequent temporary errors, the connectionerror and ratelimiterror , by default already you don't need the break error handler to automatically retry these types of errors to automatically retry the connectionerror and ratelimiterror , you only need to enable incomplete executions in scenario settings you can read more about automatic retry in the article about incomplete executions docid 6zznn7v35herrcjfccp9q {{product name}} processes the rest of the bundles in the {{scenario singular lowercase}} flow to use the break error handler in your {{scenario singular lowercase}} , you have to enable incomplete executions in {{scenario singular lowercase}} settings 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 run the example {{scenario singular lowercase}} , we would get the bundlevalidationerror if we added the break error handler to the update a record module, the break error handler would remove the bundle from the {{scenario singular lowercase}} flow the bundle that caused the error doesn't continue through the rest of the {{scenario singular lowercase}} instead, {{product name}} creates an incomplete execution to store the error type, mappings, and the remaining {{scenario singular lowercase}} flow {{product name}} would then process the remaining bundles in the {{scenario singular lowercase}} flow for more information about error handling strategies check the overview of error handling docid 7 hehdtuu2xyys8 qurub store the {{scenario singular lowercase}} when an error happens with the break error handler, you can store the remaining {{scenario singular lowercase}} flow in the {{scenario singular lowercase}} incomplete executions when an error happens {{product name}} also stores the error message, {{scenario singular lowercase}} mappings, and data you can finish the {{scenario singular lowercase}} run in the incomplete executions tab manually or {{product name}} can finish the run automatically for example, the following {{scenario singular lowercase}} outputs an error in the data store app module to store the {{scenario singular lowercase}} as an incomplete execution, follow the steps right click the module that is causing the error in the menu, select add error handler select the break error handler optional in the error handler settings, select if you want to automatically finish the incomplete executions for automatic completions, you can set the number of attempts and the time delay between them confirm the break handler settings with the ok button enable storing of incomplete executions in {{scenario singular lowercase}} settings save your {{scenario singular lowercase}} you added the break error handler to your {{scenario singular lowercase}} when an error occurs in the data store module, {{product name}} creates an incomplete execution the {{scenario singular lowercase}} incomplete execution contains the error message, {{scenario singular lowercase}} mappings and data if you use the automatic {{scenario singular lowercase}} completion, {{product name}} attempts to finish the {{scenario singular lowercase}} automatically