Break error handler
The Break error handler removes the erroring bundle from the Action Flow flow. Celonis platform stores the error message, mappings and the remaining Action Flow flow as an incomplete execution. Depending on the Break error handler settings, Celonis platform retries the incomplete scenario 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.
Note
Make 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 the RateLimitError, you only need to enable incomplete executions in scenario settings.
You can read more about automatic retry in the article about incomplete executions.
Celonis platform processes the rest of the bundles in the Action Flow flow.
To use the Break error handler in your Action Flow, you have to enable incomplete executions in Action Flow settings.
For example: This demo Action Flow contains five modules. The Action Flow 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
nullvalue into the required Key field, which always creates theBundleValidationError.Slack - Send a message: Sends a message to a private testing channel.
This is how the example Action Flow looks:
When we would run the example Action Flow, 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 Action Flow flow. The bundle that caused the error doesn't continue through the rest of the Action Flow. Instead, Celonis platform creates an incomplete execution to store the error type, mappings and the remaining Action Flow flow.
Celonis platform would then process the remaining bundles in the Action Flow flow.
For more information about error handling strategies check the overview of error handling.
Store the Action Flow when an error happens
With the Break error handler, you can store the remaining Action Flow flow in the Action Flow incomplete executions when an error happens. Celonis platform also stores the error message, Action Flow mappings and data.
You can finish the Action Flow run in the incomplete executions tab manually or Celonis platform can retry the run automatically.
For example, the following Action Flow outputs an error in the Data Store app module:
To store the Action Flow 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 Action Flow settings.
Save your Action Flow.
You added the Break error handler to your Action Flow. When an error occurs in the Data store module, Celonis platform creates an incomplete execution. The Action Flow incomplete execution contains the error message, Action Flow mappings and data.
If you use the automatic Action Flow completion, Celonis platform attempts to retry the Action Flow run automatically.