Symptoms
When using an exception rule at the process level, this item is designed to execute the code in the exception rule any time the process throws an error. However, when a process goes into error state on a client event with the message "An activity with a client event should at least have one destination", the exception rule does not get fired.
Diagnoses
This behavior is by design.
Resolution
This behavior is not a bug and happens by design. This is because Exception Rules are designed to not interfere and catch any errors thrown by the workflow engine functionality/logic (i.e. the No Destination or invalid destinations message).
There’s a difference between workflow engine functionality – and errors raised by it vs. peripheral code execution – and errors raised by that.
The Exception Rules will catch and act on peripheral code execution failures but will not (and cannot) interfere with workflow execution logic.
There currently is no feature or plan to change the exception rule functionality logic at this time. However, an alternative may be to utilize this plugin from the K2 Community site: http://community.k2.com/t5/K2-blackpearl/SourceCode-Logging-Plug-in/ba-p/481
