Uploaded image for project: 'Serverless logic'
  1. Serverless logic
  2. SRVLOGIC-4

[core] Workflow domain-specific error handling

    XMLWordPrintable

Details

    • Feature
    • Resolution: Done
    • Critical
    • 1.24.0
    • None
    • serverless-workflow
    • None
    • False
    • None
    • False
    • 0
    • 0% 0%
    • 2022 Week 32-34 (from Aug 8)

    Description

      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.

      Attachments

        Issue Links

          incorporates

          Feature Request - Feature requests from customers and/or users KOGITO-7453 Introduce HTTP code for Error Handling on Serverless Workflows

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-7557 RestWorkItemHandler does not propagate exceptions/errors from invoked service

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7253 [KSW-Guides] Understanding workflow error handling

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SRVLOGIC-17 [use case] Handling infrastructure errors outside of workflows (stretch goal)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ftirados Francisco Javier Tirado Sarti
              ibek1@redhat.com Ivo Bek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: