Commit error handler
The Commit error handler stops the Action Flow run and commits changes in your database apps. If your Action Flow is not using apps that support transactions, like MySQL or Data store, the Commit error handler just stops the Action Flow.
With the Commit error handler, you can stop the Action Flow when an error happens. Celonis platform saves changes in the database apps in your Action Flow and doesn't process the rest of the bundles in the Action Flow flow.
For example, the following Action Flow outputs an error in the Data Store app module:
To stop the Action Flow and save changes, follow the steps:
Right-click the module that is causing the error. In the menu, select Add error handler.
Select the Commit error handler.
Save your Action Flow.
You added the Commit error handler to your Action Flow. When an error occurs in the Data store module, the Action Flow stops and Celonis platform saves changes in modules that support transactions.
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.Having two data store modules doing the same thing, but one of them failing, will make a good example for the Commit and Rollback error handlers.
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:
