Boomi Tip: Boomi Sub-Process Error Reporting Behavior

In this blog, we will look at how Boomi handle an error execution of a sub process and how it affects the parent process. Let’s separate this into 2 categories: Synchronous and Asynchronous Execution

 

Synchronous Process

Data Passthrough
As we all know that a Data Passthrough sub process will accept the document from the parent process. In this, if there document failed in the sub process, it will also stop the parent process with error regardless of the “Abort if the process fails” option.

No Data/Connector Call
If the “Abort if the process fails” option is enabled, the sub process will fail with an error. The parent process will also fail with an error and it will stop at the process call shape (where the sub process is being called). However, if the “Abort if the process fails” option is disabled, only the sub process will be error-ed.

 

async_error_2
Figure 1: Error Log for Synchronous Process

 

Asynchronous Process

Data Passthrough
This is not supported in asynchronous execution

No Data/Connector Call
If the “Abort if the process fails” option is enabled, the sub process will fail with an error and this will be reported back to the parent process. And, the parent process will be flagged as error only after the parent process has finished executed all the process paths. Please see Figure 2 for the sample error logs.

 

async_error_1
Figure 2: Error log for Asynchronous Process