Error handling
Error handlers
Quick error handling reference
1 min
the following table provides a quick reference to working with error handlers in 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 docid\ sqi vchjtdyg29tn0ylet break stores the subsequent modules as an docid 6zznn7v35herrcjfccp9q set the automatic completion to yes to get similar functionality as a retry otherwise, you have to resolve incomplete executions manually processes the rest of the bundles in the flow normally the scenario ends with the "warning" status check the docid\ hxe6n1fool691glswodgy for further information commit stops the run and commits all changes doesn't process the rest of the modules in the flow the scenario ends with the "success" status check the docid 2iifydg6v5dw 94 jkm2i for further information ignore ignores the error the bundle doesn't continue in the flow processes the rest of the bundles in the flow normally the scenario ends with the "success" status check the 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 processes the rest of the bundles in the flow normally the scenario ends with the "success" status check the docid\ wr8aaeme2ptfar38vxd3p for further information rollback stops the run and reverts changes in all modules that support transactions doesn't process the rest of the modules in the flow stops scheduling the after the rollback activates for the 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 docid 6zznn7v35herrcjfccp9q disabled