This topic describes the overview and examples of error handling during workflow integration.
Expected or unexpected errors may occur in the workflow integration of CloudFlow. You can retry the current state or move to the next state based on the scenario. The
FnF.ALL keyword is a special option that hits all errors.
The following table describes the attributes of the error handling logic.
The errors that can be hit.
The description of the error.
describe it here
The retry policy. This attribute and the Next attribute are mutually exclusive. This attribute has a lower priority than the Next attribute.
The next state that is executed after the current state is complete. This attribute and the Retry attribute are mutually exclusive. This attribute has a higher priority than the Retry attribute.
The output constructor. This attribute is used together with the Next attribute.
The maximum number of retries.
The first backoff delay.
The backoff exponent.
The OutputConstructor attribute is used together with the Next attribute. If an error occurs in a state, no expected outputs are generated in the state. The flow cannot proceed even if the flow transits to the next state. In this case, you can use the OutputConstructor attribute to construct an output and use the output as the input of the next state.
- Type: Task
Description: my retry policy
Description: my catch policy
- Type: Pass
In the preceding example, if an error occur in the Mytestfc integration and the error hits MyCustomException, the system retries the state up to five times based on the retry policy. After the maximum number of retries is exhausted, the flow ends.
If other errors occur, the errors hit
FnF.ALL. The system uses the OutputConstructor attribute to construct an output and uses the output as the input of the Pass1 state. Then, the flow transits to the Pass1 state.