The on_failure edge case of the imperative workflow is unreachable. It means that if your previous step fails it will keep executing on_success edge cases.

How to reproduce :

Run this CBA example : cba.zip

See workflow steps:

    "workflows" : {
      "multi-step" : {
        "steps" : {
          "execute-script" : {
            "description" : "Execute Remote Python Script",
            "target" : "execute-remote-python",
            "on_failure" : [ "resolve-stuff" ]
          },
          "resolve-stuff" : {
            "description" : "Component resource resolution regression test",
            "target" : "resource-resolution"
          }
        },
        "inputs" : { },
        "outputs" : {
          "meshed-template" : {
            "type" : "json",
            "value" : {
              "get_attribute" : [ "resource-resolution", "assignment-params" ]
            }
          }
        }
      }
    }

Expected behaviour :

1. Runs the execute-script workflow step that executes the execute-remote-python node template
   • The executed python script defined will raise an exception to make the execute-script step fail
   • Imperative workflow should then triggers on_failure edge cases
2. Workflow step resolve-stuff runs and execute resource-resolution node template.
   • resolve-stuff should succeed and return his output

Actual behaviour:

1. execute-script workflow step runs
   • It fails as expected
   • on_success are triggered
2. Execution fails because no on_success edge cases are defined

See execution logs: