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

[core] Workflow domain-specific error handling

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Critical Critical
    • 1.24.0
    • None
    • serverless-workflow
    • 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.

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

              Created:
              Updated:
              Resolved: