Exception handling allows you to define sequences of operators for predefined exceptions on operators in a process, such as Failure, Abort, or Unexpected outcome. You can also create a default sequence of operators to perform for any exceptions lacking an explicit sequence. While the Workflow module processes an exception, it pauses execution of any other operators in the process.
Exception handling uses priorities when evaluating exit conditions on an operator. The following table lists the exception types:
|
Priority |
Exception Type |
Occurs When |
|---|---|---|
|
1 |
System Exception |
There is an incorrect touchpoint name, an unreachable agent, or any type of communications failure. |
|
2 |
Unidentified Response |
There is no exit link for a particular exit condition. |
|
3 |
Aborted |
An operator aborts or a user aborts an operator. |
|
4 |
Timeout |
An operation times out and there is no path defined from the timeout port to the main flow. |
When a process operator experiences an exception, the Workflow module takes the following actions:
|
Priority |
Matches |
Action |
|---|---|---|
|
1 |
Exception handler defined in the process object. |
Runs the exception handler defined in the process object. |
|
2 |
Exception handler defined on the default process object for the orchestrator running the Workflow module. |
Runs the exception handler defined in the default process object for the orchestrator. |
|
3 |
None |
Ignores the exception. The Workflow module continues processing the process. |
|
Copyright © 2014 CA.
All rights reserved.
|
|