-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
False
-
-
False
-
Will be fixed with kogito-7557
-
-
---
-
---
Consider a workflow with multiple error definitions:
"errors": [
{
"name": "odd number",
"code": "java.lang.RuntimeException"
},
{
"name": "bad request",
"code": "HTTP:400"
}
],
and references to these errors in different nodes:
{
"name": "checkEven",
"type": "operation",
"actions": [
{
"name": "checkEvenAction",
"functionRef": {
"refName": "isEven",
"arguments": {
"number": "$.number"
}
}
}
],
"transition": "even",
"onErrors": [
{
"errorRef": "odd number",
"transition": "odd"
}
]
},
and
{
"name": "publish",
"type": "operation",
"actions": [
{
"name": "publishAction",
"functionRef" : {
"refName": "publishPerfectSquare",
"arguments": {
"type": "$.numberType",
"number": "$.number"
}
}
}
],
"end": true,
"onErrors": [
{
"errorRef": "bad request",
"transition": "setError"
}
]
},
While the first exception is properly handled, the second one is not, and the process fails to proceed on the defined error transition.
- is incorporated by
-
-
- Resolved
-
