Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-1014 Orchestrator UI/UX improvements
  3. FLPATH-936

Add ability to re-trigger workflows in ERROR state

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • None
    • None
    • None

      Instances in ERROR state can be re-triggered (there is an API for that). It is different from our "Rerun" button because it does not create a new instance. Instead, it reruns the current instance starting from the failed node. Users can also provide new input values.

      This task is very similar to FLPATH-882, the difference is that it must rerun the current instance rather than create a new one.

      NOTE: The retrigger operation does not seem to be working properly (see this issue).

        1. image-2024-05-07-14-35-28-003.png
          image-2024-05-07-14-35-28-003.png
          65 kB
        2. image-2024-05-28-14-05-30-773.png
          image-2024-05-28-14-05-30-773.png
          133 kB
        3. screenshot-1.png
          screenshot-1.png
          232 kB
        4. screenshot-2.png
          screenshot-2.png
          191 kB

            yuzhao583 Yu Zhao
            gcaponet Guilherme Caponetto
            Yona First Yona First
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: