This article covers some advanced error handling techniques that involve filtering and nesting.
There are 2 kinds of filtering that can take place on an error handler route:
- Adding a filter to the error handler routeYou can use a filter to control which errors are handled by the error handler route. This allows you to process only specific types of errors. If an error does not pass through the filter, it will be treated as if there is no error handler route defined for the given module.
- Adding a RouterA router allows you to add new routes to a scenario so you can branch your flow into several routes and process the data within each route differently. followed by filters to the error handler route
As you can see above, the error takes place at the Create a folder module (A), which has a regular route and an error handler route. The latter is followed by a router with one route that has a filter that defines a specific type of error (Data Error Takes Place), and the other which is the default route for all other errors. The first route ends with the Resume directive which contains substitute values for the scenarioA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive. to resume from module A (Create a folder), while the second route ends with the Rollback directive which stops the scenario execution immediately.
See the Error processing section for further information on various error types and on how Boost.space IntegratorPart of the Boost.space system, where you can create your connections and automate your processes. processes and evaluates them.
Here’s how the above scenario is set up:
Use an existing Dropbox folder to upload a file instead of creating a new one
If you use the Create a folder module on Dropbox and a folder with the same name already exists, the module will throw a Data Error as shown below:
Here’s the complete scenario:
- The Tool > Set Variable module contains the folder name
- The HTTP > Get a file module fetches the file that needs to be uploaded to the folder
- The Dropbox > Create a folder module throws an error if a folder already exists with the same name as the one mapped in the module
- The error handler route (transparent bubbles) contains a router to filter the errors
- The first route is for a specified type of error called Data Error as we know of it already:1. If a Data Error takes place and the error details pass through the filter, the Dropbox > List all files/subfolders in a folder module lists all folders in Dropbox.
2. The subsequent filter matches the folder names
3. The Resume directive specifies the folder ID and folder path of the existing folder and the scenario execution resumes from the Dropbox > Create a folder module but instead of trying to create a new folder, this time it uses the values from the Resume directive to move to the next module and upload the file in the existing folder.
- The second route is for all other errors and ends with the Rollback directive which results in stopping the scenario immediately.
Below is a detailed explanation of the 5th statement:
5. In order to use the existing folder in your subsequent modules (Upload a file below), you need to add an error handler route to the module and fetch the folder path to be mapped into the Resume directive module that follows:
5.1 The filter on the first route is set to only handle the particular error (Data Error) that appears when a folder with the same name already exists:
5.2 The Dropbox > List all files in a folder module is configured to return all the folders in the target folder. The following filter only passes on the one we were originally trying to create (the folder name is stored in the 33. Folder Name item):
5.3 Eventually, the Resume directive supplies the Folder path as the output for the failed module. Note that the Folder ID has been left blank since it is not needed by the ‘Upload a file’ module:
Regardless of where a module is located, error handler routes can be created and implemented on all modules, except routersA router allows you to add new routes to a scenario so you can branch your flow into several routes and process the data within each route differently.. Thus, it is possible to create an error handler route for a module that is already part of an existing error handler route created for another module.
Here’s an example of a nested error handler route:
In the above scenario, the second error handler route is nested under the first error handler route. So, if the Dropbox > Create a folder module encounters an error, the execution moves to Route 1, if the Data Error Takes Place filter is passed, the next module is executed followed by the Resume directive module if an error does not take place with the Dropbox > List all files/subfolders in a folder module.
However, if an error does take place with this Dropbox module, then the execution moves to Error Handler Route 2 and ends with the Ignore directive. It is obvious that the Resume directive module is not executed in this case.
That is a combination of filtering and nesting error handlers.