Question

When configuring a retry scope for a network-dependent activity, what is the primary difference in outcome between a system exception and a business exception?

Accepted Answer

A Retry Scope is a container activity designed to repeat a nested activity until it succeeds or a defined number of retries is exhausted. When a network-dependent activity is placed inside a Retry Scope, the treatment of exceptions depends on the type of error encountered. A system exception represents a technical issue, such as a network timeout or a server being temporarily unreachable. Because these errors are often transient, the Retry Scope is specifically designed to catch system exceptions and automatically trigger another attempt to execute the activity. In contrast, a business exception represents a logical error or a data-related issue, such as an account not being found or a validation failure. Because these errors are caused by incorrect input or state rather than technical instability, they are not considered transient. Consequently, a Retry Scope does not attempt to retry the activity when a business exception occurs; instead, it immediately stops the retries and propagates the exception to the next level of the workflow. Therefore, the primary difference is that a system exception forces the scope to perform another attempt, while a business exception terminates the retry process immediately.

Home → All Courses → Programming Courses → Robotic Process Automation (RPA) Development → Flashcard

When configuring a retry scope for a network-dependent activity, what is the primary difference in outcome between a system exception and a business exception?