top of page
  • Writer's pictureAlex James

Boomi Try Catch "Document Errors" or "All Errors" - What should you use when?

Updated: Mar 1

You introduce a Try Catch shape in Boomi to manage exceptions and invoke retries. When a process encounters any errors in the try path, the control is passed to the catch path after specified retries.

A process without a try catch terminates in the event of an error and such executions are marked with a red dot in the process reporting.

The try catch shape “Failure Trigger” setting has two options, “Document Errors” and “All Errors”. This setting qualifies whether an exception is eligible to be sent down to the errors path.

✅“Document Errors” Failure Trigger

🔹As the name suggests, only document errors are qualified to be sent down to the error path. Situations such as documents failing at connector during update because of invalid id are examples of document errors.

🔹Any errors at the process level result in process execution getting terminated and NO documents are sent down the catch path.

🔹If you have a catch logic in your process, then it will not be executed during process level errors.

🔹“Document Errors” needs be set if you wish to catch only document errors and terminate execution for all process level errors.

✅“All Errors” Failure Trigger

🔹Both process level errors and document errors are qualified to be caught in this setting. Scripting errors such as null pointer errors are examples of process level errors.

🔹During a process level exception, all the source documents before the try catch would be sent down the catch path whereas error only documents for Document level exception.

🔹“All Errors” needs to be set when you would like to act on all errors at the catch path.

Though “Document Errors” is the default try catch “Failure Trigger” setting, the “All Errors” setting has a wider scope in catching errors in a simple try catch scenario. Every integration exception handling scenario is unique involving a variety of connectors, nested Try Catch shapes, sub process calls and it is important to test all exception cases and configure the right failure trigger setting to achieve the desired outcome.

Should you have anything more to add, please write in comments.

571 views0 comments


bottom of page