Details
-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
User Story (Required on creation):
When using external tasks with error expressions, they can be triggered on a ExternalTaskService#handleFailure call. However, the expressions themselves can fail, which result in a failed API call. Since #handleFailure is already a call that is used in the exceptional case, it is hard for callers to escalate any further.
Example: In case an RPA bot fails, this should always be successfully handled by the process engine which orchestrates the bots to give an operator a consistent view of their bot state (assuming the engine is generally operational). It should not lead to the RPA bridge having to deal with the problem (which means it remains invisible to a process operator).
Functional Requirements (Required before implementation):
- In a handleFailure call, when an error expression evaluation fails, this continues the regular #handleFailure logic instead of raising an exception to the API caller
Technical Requirements (Required before implementation):
- The failed error expression evaluation is logged in the engine
- This behavior is documented in Javadoc and user guide, because it differs from the norm