The Throw activity allows you to throw an exception. The exception can be a potential exception for any of the activities in the orchestration process, or you can define a new exception in the Throw activity.
The Throw activity is particularly useful if an error in business logic occurs during processing. For example, orders over $10,000 must include a credit check of the customer. If the credit check returns a credit score that is too low, the order is canceled. The Throw activity can be used to return a fault message to the order requestor stating that the credit check has failed.
Figure 28 illustrates this example.