-
Bug
-
Resolution: Done
-
Major
-
None
-
1.4.0
-
False
-
-
False
-
-
-
Proposed
Description of the problem:
When workflow fails with error, and it is retriggered from the failure point, the workflow status remains in Error. The only visual indicator to the user that the workflow is continuing to run is the Workflow Progress section is being updated and progressing, which the user might easily miss without scrolling down:
How reproducible: 100%
Steps to reproduce:
1. Deploy orchestrator using 1.4.0-rc13
2. Deploy workflow like mta7 and cause it to fail with Error
3. Fix the cause of the error, and retrigger the workflow
Actual results:
Workflow status stays in Error after retrigger. If the workflow completes it moves to Completed state, but the fact that it is running again is not clear to the user. The Results section has failure message until completion.
Expected results:
The workflow's state should move back to Active instead of Error, and/or the Results pane should have the "Workflow is running" box again to clearly show the user that the workflow is running again.
- is depended on by
-
FLPATH-1683 Add an option to retrigger workflows
-
- Closed
-