Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-2136

Retriggering at failure point adds another failed node step to workflow progress section

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Description of the problem:
      When retriggering a workflow at the failure point, an additional fail node is added to the workflow progress point.

      How reproducible: 100%

      Steps to reproduce:

      1. Deploy orchestrator 1.4.0-rc13

      2. Deploy workflow like MTA, and change URL to local service in mta7 props CM 

      3. When workflow fails with error, edit the URL in the cm to point to correct service

      4. Retrigger the workflow in the UI
       

      Actual results: The workflow continues executing, but an additional extra "failure" node is added in the workflow progress section at the point it was retriggered:

      Expected results: After retrigger execution should continue normally without failure node that is confusing for the user.

              ydayagi yaron dayagi
              yfirst Yona First
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: