Quick error handling reference

the following table provides a quick reference to working with error handlers in {{product name}} if you want to learn more about individual error handlers, check the dedicated articles in this section of the help center if you want to learn more about error handling, you can start with the introduction to errors and warnings docid\ sqi vchjtdyg29tn0ylet break {{product name}} stores the subsequent modules as an incomplete executions docid 6zznn7v35herrcjfccp9q set the automatic completion to yes to get similar functionality as a retry otherwise, you have to resolve incomplete executions manually {{product name}} processes the rest of the bundles in the {{scenario singular lowercase}} flow normally the scenario ends with the "warning" status check the error handler docid\ hxe6n1fool691glswodgy for further information commit {{product name}} stops the {{scenario singular lowercase}} run and commits all changes {{product name}} doesn't process the rest of the modules in the {{scenario singular lowercase}} flow the scenario ends with the "success" status check the error handler docid 2iifydg6v5dw 94 jkm2i for further information ignore {{product name}} ignores the error the bundle doesn't continue in the {{scenario singular lowercase}} flow {{product name}} processes the rest of the bundles in the {{scenario singular lowercase}} flow normally the scenario ends with the "success" status check the error handler docid\ xzfc2uhei4kmsmhydbnmp for further information resume specify a substitute mapping for when the module outputs an error the substitute data continue through the rest of the {{scenario singular lowercase}} {{product name}} processes the rest of the bundles in the {{scenario singular lowercase}} flow normally the scwnario ends with the "success" status check the error handler docid\ wr8aaeme2ptfar38vxd3p for further information rollback {{product name}} stops the {{scenario singular lowercase}} run and reverts changes in all modules that support transactions ( types of modules docid\ pdopibceckcbomppkplmy ) {{product name}} doesn't process the rest of the modules in the {{scenario singular lowercase}} flow {{product name}} stops scheduling the {{scenario singular lowercase}} after the rollback activates for the overview of error handling docid 7 hehdtuu2xyys8 qurub in a row the scenario ends with the "error" status rollback is the default error handling if you don't set any error handling and when you keep incomplete executions docid 6zznn7v35herrcjfccp9q disabled