-
Feature
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
None
-
False
-
2022 Week 32-34 (from Aug 8)
Motivation
Workflows should fail only in case of unexpected errors. Explicit error handling with known errors defines the behavior of what should happen in case of errors inside workflows. These errors are “domain-specific” and closely related to the workflows - “Order not found”, or “Item not in inventory”.
Goal
Enable error handling in workflows to define the unhappy paths
Scenarios
As a developer, I need to define what should happen in case of an error coming from a service so that the workflow can take remediate actions and end the workflow gracefully.
Expected outcomes
Workflows can define known domain-specific errors
Errors can be defined externally using a json and inline in the workflow
It’s possible to specify error codes to map domain-specific errors to concrete underlying technical errors.
It’s possible to react onErrors in all supported workflow states
In case of an unexpected error the workflow is aborted with an error.
- incorporates
-
KOGITO-7453 Introduce HTTP code for Error Handling on Serverless Workflows
- Resolved
-
KOGITO-7557 RestWorkItemHandler does not propagate exceptions/errors from invoked service
- Resolved
-
KOGITO-7253 [KSW-Guides] Understanding workflow error handling
- Resolved
- is related to
-
SRVLOGIC-17 [use case] Handling infrastructure errors outside of workflows (stretch goal)
- Closed