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

Treat the ERROR state as a non-final state

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      We should treat the ERROR state as a non-final. It means that instances in this state are still "active", i.e, they don't have an "end date". Also, instances in ERROR state can be aborted (currently, we are enabling the ABORT button only for the ACTIVE state).

              gcaponet Guilherme Caponetto
              gcaponet Guilherme Caponetto
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: